Skip to main content

Debugging enabled in production

Description​

The system has the debug mode active which generates an information leak when an error is generated.

Impact​

Obtain sensitive information such as stacktraces and versions of the systems used.

Recommendation​

Make sure that debugging mode is not enabled in the production environment and remove statements or portions of code that are executing in debugging mode.

Threat​

External attacker with access to the application.

Expected Remediation Time​

⌚ 15 minutes.

Score​

Default score using CVSS 3.1. It may change depending on the context of the vulnerability.

Base​

  • Attack vector: N
  • Attack complexity: L
  • Privileges required: L
  • User interaction: N
  • Scope: U
  • Confidentiality: L
  • Integrity: N
  • Availability: N

Temporal​

  • Exploit code madurity: X
  • Remediation level: X
  • Report confidence: X

Result​

  • Vector string: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N/E:X/RL:X/RC:X
  • Score:
    • Base: 4.3
    • Temporal: 4.3
  • Severity:
    • Base: Medium
    • Temporal: Medium

Code Examples​

Compliant code​

Disable any plugin or dependencies that could allow debugging mode in the application production code

Non compliant code​

Debugging mode is active in a production environment

<build>
    <finalName>remote-debugging</finalName>
    <plugins>
        <plugin>
          <groupId>org.springframework.boot</groupId>
          <artifactId>spring-boot-maven-plugin</artifactId>
        </plugin>
    </plugins>
</build>

Requirements​

free trial

Search for vulnerabilities in your apps for free with our automated security testing! Start your 21-day free trial and discover the benefits of our Continuous Hacking Machine Plan. If you prefer a full service that includes the expertise of our ethical hackers, don't hesitate to contact us for our Continuous Hacking Squad Plan.