ASP.NET Misconfiguration: Creating Debug Binary

Opis

Debugging messages help attackers learn about the system and plan a form of attack.

ASP .NET applications can be configured to produce debug binaries. These binaries give detailed debugging messages and should not be used in production environments. Debug binaries are meant to be used in a development or testing environment and can pose a security risk if they are deployed to production.

Skutki

• Confidentiality

  Read Application Data

  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.

Zapobieganie

• System Configuration

  Avoid releasing debug binaries into the production environment. Change the debug mode to false when the application is deployed into production.

Słabość nadrzędna

• CWE-489 Active Debug Code

Kiedy powstaje

• Implementation
• Build and Compilation

Dotyczy

ASP.NET

Źródła

1. Seven Pernicious Kingdoms: A Taxonomy of Software Security Errors — Katrina Tsipenyuk, Brian Chess, Gary McGraw, NIST, 2005
2. Creating an ASP.NET debug binary may reveal sensitive information — CodeQL