CWE-489 Active Debug Code

The product is released with debugging code still enabled or active.

• Confidentiality, Integrity, Availability, Access Control, Other: Bypass Protection Mechanism, Read Application Data, Gain Privileges or Assume Identity, Varies by Context — Active debug code can create unintended entry points or expose sensitive information. The severity of the exposed debug code will depend on the particular instance. At the least, it will give an attacker sensitive information about the settings and mechanics of web applications on the server. At worst, as is often the case, the debug code will allow an attacker complete control over the web application and server, as well as confidential information that is accessed by either of these.

• [Build and Compilation, Distribution] Remove debug code before deploying the application.

• Automated Static Analysis: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)

• CVE-2024-44092: smartphone is built for production with debugging code present, allowing local privilege escalation • CVE-2024-36475: network hub contains active debug code, which allows users to execute arbitrary OS commands using a debug function • CVE-2024-29075: Mesh Wi-Fi router has active debug code, allowing attackers to modify device settings