CWE-12 詳細

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

背景の詳細

導入モード

Implementation
Operation

適用可能なプラットフォーム

言語

名前： ASP.NET (Undetermined)

一般的な結果

潜在的な緩和策

Phases : 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.
Phases : Architecture and Design
Do not attempt to process an error or attempt to mask it.
Phases : Implementation
Verify return values are correct and do not supply sensitive information about the system.

検出方法

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

脆弱性マッピングノート

理由 : This CWE entry is at the Variant level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
コメント : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.

参考文献

REF-6

Seven Pernicious Kingdoms: A Taxonomy of Software Security Errors
Katrina Tsipenyuk, Brian Chess, Gary McGraw.
https://cwe.mitre.org/documents/sources/SevenPerniciousKingdoms.pdf

REF-65

19 Deadly Sins of Software Security
M. Howard, D. LeBlanc, J. Viega.

REF-66

ASP.NET Misconfiguration: Missing Custom Error Handling
OWASP, Fortify Software.
https://www.owasp.org/index.php/ASP.NET_Misconfiguration:_Missing_Custom_Error_Handling

登録情報

変更履歴