Leftover Debug Code

Last revision (mm/dd/yy): //

Vulnerabilities Table of Contents

Description
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
TBD

Examples
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

 * Attack 1
 * Attack 2

Related Vulnerabilities

 * Vulnerability 1
 * Vulnerabiltiy 2

Related Controls

 * Control 1
 * Control 2

Related Technical Impacts

 * Technical Impact 1
 * Technical Impact 2