logo

Insertion of Sensitive Information Into Debugging Code

Draft Base
Structure: Simple
Description

The product inserts sensitive information into debugging code, which could expose this information if the debugging code is not disabled in production.

Extended Description

When debugging, it may be necessary to report detailed information to the programmer. However, if the debugging code is not disabled when the product is operating in a production environment, then this sensitive information may be exposed to attackers.
Common Consequences 1
Scope: Confidentiality

Impact: Read Application Data
Detection Methods 1
Automated Static AnalysisHigh
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.)
Potential Mitigations 2
Phase: Implementation
Do not leave debug statements that could be executed in the source code. Ensure that all debug information is eradicated before releasing the software.
Phase: Architecture and Design

Strategy: Separation of Privilege

Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
Demonstrative Examples 1

ID : DX-131

The following program changes its behavior based on a debug flag.

Code Example:

Bad
JSP
jsp
The code writes sensitive debug information to the client browser if the "debugEnabled" flag is set to true .
Observed Examples 3
CVE-2004-2268Password exposed in debug information.
CVE-2002-0918CGI script includes sensitive information in debug messages when an error is triggered.
CVE-2003-1078FTP client with debug option enabled shows password to the screen.
Applicable Platforms
Languages:
Not Language-Specific : Undetermined
Modes of Introduction
Implementation
Related Weaknesses
ChildOf: Exposure of Sensitive Information to an Unauthorized Actor (CWE-200)
Taxonomy Mapping
  • PLOVER
  • OWASP Top Ten 2007
  • OWASP Top Ten 2004
  • Software Fault Patterns
Notes
RelationshipThis overlaps other categories.