This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit

Difference between revisions of "Leftover Debug Code"

Jump to: navigation, search
m (Moved page into the right category. See Java space page for me details. Content has not been reviewed in this edit.)
Line 82: Line 82:
[[Category:Code Quality Vulnerability]]
[[Category:Code Quality Vulnerability]]
[[Category:OWASP Java Project]]

Latest revision as of 11:47, 10 November 2017

This is a Vulnerability. To view all vulnerabilities, please see the Vulnerability Category page.

This article includes content generously donated to OWASP by MicroFocus Logo.png

Last revision (mm/dd/yy): 11/10/2017

Vulnerabilities Table of Contents


Debug code can create unintended entry points in a deployed web application.

A common development practice is to add "back door" code specifically designed for debugging or testing purposes that is not intended to be shipped or deployed with the application. When this sort of debug code is accidentally left in the application, the application is open to unintended modes of interaction. These back door entry points create security risks because they are not considered during design or testing and fall outside of the expected operating conditions of the application.

Risk Factors



The most common example of forgotten debug code is a main() method appearing in a web application. Although this is an acceptable practice during product development, classes that are part of a production J2EE application should not define a main().

Related Attacks

Related Vulnerabilities

Related Controls

Related Technical Impacts