Active debug code can create unintended entry points or expose sensitive information. The severity of the exposed debug code will depend on the particular instance. At the least, it will give an attacker sensitive information about the settings and mechanics of web applications on the server. At worst, as is often the case, the debug code will allow an attacker complete control over the web application and server, as well as confidential information that either of these access.

Remediation

To remediate this vulnerability, all debug functionality, test hooks, and development backdoors should be removed or disabled before deployment to production environments. Secure build and release processes should ensure that debugging features are not included in production builds, and configuration reviews should verify that debug modes are disabled prior to distribution.

Metadata

• Severity: high
• Slug: active-debug-code-left-in-production

CWEs

• 489: Active Debug Code
• 1295: Debug Messages Revealing Unnecessary Information

OWASP

• A05:2021: Security Misconfiguration