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.
FTP client with debug option enabled shows password to the screen.
Related Attack Patterns (CAPEC)
N/A
Attack TTPs
N/A
Modes of Introduction
Phase
Note
Implementation
N/A
Common Consequences
Impact: Read Application Data — Notes:
Potential Mitigations
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. (N/A)
Architecture and Design: 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. (N/A)
Applicable Platforms
None (Not Language-Specific, Undetermined)
Demonstrative Examples
Intro: The following program changes its behavior based on a debug flag.
Body: The code writes sensitive debug information to the client browser if the "debugEnabled" flag is set to true .
<% if (Boolean.getBoolean("debugEnabled")) { %> User account number: <%= acctNo %> <% } %>