Difference between revisions of "Leftover Debug Code"

Jump to: navigation, search
Line 1: Line 1:
[[ASDR Table of Contents]]
[[ASDR Table of Contents]]

Revision as of 20:39, 17 February 2009

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

This article includes content generously donated to OWASP by Fortify.JPG.

ASDR Table of Contents

Last revision (mm/dd/yy): 02/17/2009


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