CWE-215
Insertion of Sensitive Information Into Debugging Code
AI Translation Available
The product inserts sensitive information into debugging code, which could expose this information if the debugging code is not disabled in production.
Status
draft
Abstraction
base
Affected Platforms
Extended Description
AI Translation
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.
Technical Details
AI Translation
Common Consequences
confidentiality
Impacts
read application data
Detection Methods
automated static analysis
Potential Mitigations
Phases:
implementation
architecture and design
Descriptions:
•
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.
•
Do not leave debug statements that could be executed in the source code. Ensure that all debug information is eradicated before releasing the software.