CWE-215: Insertion of Sensitive Information Into Debugging Code
Base
The product inserts sensitive information into debugging code, which could expose this information if the debugging code is not disabled in production.
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.
Consequences
- Confidentiality: Read Application Data
How to prevent it
- 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.
- 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.
Recent advisories
- GHSA-x6g4-f6q3-fqvv — NATS credentials are exposed in monitoring port via command-line argv
- GHSA-mjvc-j6rv-9xj8 — Insertion of Sensitive Information Into Debugging Code in Microweber
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor