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规则。