CWE-11 ASP.NET Misconfiguration: Creating Debug Binary

The product has an ASP .NET component that contains a debug binary.

• Confidentiality: Read Application Data — Debug binaries give detailed debugging messages, which is useful in a development or testing environment, but can pose a security risk if the debug binary is deployed to production. Attackers can leverage the additional information they gain from debugging output to mount attacks targeted on the framework, database, or other resources used by the application.

• [System Configuration] Avoid releasing debug binaries into the production environment. Change the debug mode to false when the application is deployed into production.

• 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.)