The product is deployed to unauthorized actors with debugging code still enabled or active, which can create unintended entry points or expose sensitive information.
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 product. 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 product.
This term originates from Seven Pernicious Kingdoms
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| CanPrecede | Allowed | B | 215 | Insertion of Sensitive Information Into Debugging Code |
| ChildOf | Discouraged | P | 710 | Improper Adherence to Coding Standards |
| ParentOf | Allowed | V | 11 | ASP.NET Misconfiguration: Creating Debug Binary |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | C | 485 | 7PK - Encapsulation |
| MemberOf | Prohibited | C | 731 | OWASP Top Ten 2004 Category A10 - Insecure Configuration Management |
| MemberOf | Prohibited | C | 1002 | SFP Secondary Cluster: Unexpected Entry Points |
| MemberOf | Prohibited | C | 1006 | Bad Coding Practices |
| MemberOf | Prohibited | C | 1371 | ICS Supply Chain: Poorly Documented or Undocumented Features |
| MemberOf | Prohibited | C | 1412 | Comprehensive Categorization: Poor Coding Practices |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | BS | BOSS-294 | Not Language-Specific Weaknesses |
| MemberOf | Prohibited | BS | BOSS-305 | ICS/OT (technology class) Weaknesses |
| MemberOf | Prohibited | BS | BOSS-307 | Not Technology-Specific (technology class) Weaknesses |
| MemberOf | Prohibited | BS | BOSS-316 | Bypass Protection Mechanism (impact) |
| MemberOf | Prohibited | BS | BOSS-326 | Varies by Context (impact) |
| MemberOf | Prohibited | BS | BOSS-328 | Read Application Data (impact) |
| MemberOf | Prohibited | BS | BOSS-332 | Gain Privileges or Assume Identity (impact) |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | C | 1002 | SFP Secondary Cluster: Unexpected Entry Points |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | C | 1006 | Bad Coding Practices |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | C | 1371 | ICS Supply Chain: Poorly Documented or Undocumented Features |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | C | 485 | 7PK - Encapsulation |
| Scope | Likelihood | Impact | Note |
|---|---|---|---|
| ConfidentialityIntegrityAvailabilityAccess ControlOther | N/A | Bypass Protection MechanismRead Application DataGain Privileges or Assume IdentityVaries by Context | The severity of the exposed debug application 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 application will allow an attacker complete control over the web application and server, as well as confidential information that either of these access. |
The severity of the exposed debug application 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 application will allow an attacker complete control over the web application and server, as well as confidential information that either of these access.
Remove debug code before deploying the application.
In web-based applications, debug code is used to test and modify web application properties, configuration information, and functions. If a debug application is left on a production server, this oversight during the "software process" allows attackers access to debug functionality.
N/A
N/A
Debug code can be used to bypass authentication. For example, suppose an application has a login script that receives a username and a password. Assume also that a third, optional, parameter, called "debug", is interpreted by the script as requesting a switch to debug mode, and that when this parameter is given the username and password are not checked. In such a case, it is very simple to bypass the authentication process if the special behavior of the application regarding the debug parameter is known. In a case where the form is:
Then a conforming link will look like:
An attacker can change this to:
Which will grant the attacker access to the site, bypassing the authentication process.
| Reference | Description |
|---|
| Ordinality | Description |
|---|---|
| Indirect | N/A |
| Primary | N/A |
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
N/A
This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
In J2EE a main method may be a good indicator that debug code has been left in the application, although there may not be any direct security impact.
N/A
| Taxonomy Name | Entry ID | Fit | Entry Name |
|---|---|---|---|
| 7 Pernicious Kingdoms | N/A | N/A | Leftover Debug Code |
| OWASP Top Ten 2004 | A10 | CWE More Specific | Insecure Configuration Management |
| Software Fault Patterns | SFP28 | N/A | Unexpected access points |