Skip to content
OpenAdvisories

Weakness (CWE)

CWE-215: Insertion of Sensitive Information Into Debugging Code

Base Draft

The product inserts sensitive information into debugging code.

How to prevent it (2 mitigations)
  1. 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.

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

Source: MITRE CWE-215

0 results · Clear filters · Feed

Nothing found.