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 규칙이 없습니다.