CWE-489Active Debug Code

Description

Common consequences· 1

• 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 either of these access.

Potential mitigations· 1

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

Related CAPEC attack patterns· 2

Exploits (incoming)2

Compliance frameworks addressing this (incoming)1

(incoming)5

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.