Mishandling of Exceptional Conditions
A new category containing 24 CWEs focusing on improper error handling, logical errors, failing open, and other scenarios stemming from abnormal conditions that systems may encounter.
概要
New category for 2025. Focuses on how applications handle errors, edge cases, and exceptional conditions. Improper handling can lead to information disclosure, denial of service, or security control bypass.
攻撃者がこれを悪用する方法
攻撃パターンを理解することで、より優れた防御を構築できます。これらはセキュリティチームが監視する技術です。
Fail-open bypass
Security controls fail open when exceptions occur, allowing unauthorized access when the system encounters unexpected conditions.
Error-based information disclosure
Detailed error messages reveal internal system information, database schemas, or file paths to attackers.
Resource exhaustion
Triggering exceptional conditions repeatedly causes resource exhaustion or denial of service.
予防方法
- Implement consistent error handling across the application
- Design systems to fail securely (fail closed, not fail open)
- Handle all exception types explicitly, never use catch-all silently
- Return generic error messages to users, log detailed errors internally
- Test error handling paths with invalid, unexpected, and malicious input
- Implement timeouts and circuit breakers for external dependencies
- Validate assumptions about inputs and system state
Shoulder検出付きCWE (6)
これらのCWEにはShoulder検出ルールがあります。クリックして特定の脆弱性と修正を確認してください。
その他のマップされたCWE (18)
これらのCWEはこのカテゴリにマップされていますが、まだShoulderルールがありません。