ASP.NET Misconfiguration: Missing Custom Error Page

Opis

An ASP .NET application must enable custom error pages in order to prevent attackers from mining information from the framework's built-in responses.

Skutki

• Confidentiality

  Read Application Data

  Default error pages gives detailed information about the error that occurred, and should not be used in production environments. Attackers can leverage the additional information provided by a default error page to mount attacks targeted on the framework, database, or other resources used by the application.

Zapobieganie

• System Configuration

  Handle exceptions appropriately in source code. ASP .NET applications should be configured to use custom error pages instead of the framework default page.

• Architecture and Design

  Do not attempt to process an error or attempt to mask it.

• Implementation

  Verify return values are correct and do not supply sensitive information about the system.

Słabość nadrzędna

• CWE-756 Missing Custom Error Page

Kiedy powstaje

• Implementation
• Operation

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. 19 Deadly Sins of Software Security — M. Howard, D. LeBlanc, J. Viega, McGraw-Hill/Osborne, 2005
3. ASP.NET Misconfiguration: Missing Custom Error Handling — OWASP, Fortify Software