Insertion of Sensitive Information Into Debugging Code

CWE-215

Per technology (GHSA, All time)

84%-Pip
7%-Go
7%-Composer

Short 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.

Best practices to prevent this CWE

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.

Recently published CVEs

CVE-2024-22194

Recently published GHSA

GHSA-rgrf-6mf5-m882
GHSA-rgrf-6mf5-m882
GHSA-p3x5-5xpx-9phm
GHSA-mjvc-j6rv-9xj8

Prioritize and Uncover Reachable Vulnerabilities in Your Application Code

Identify externally reachable data flows and vulnerabilities for effective risk mitigation

Get a Demo