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.
Überblick
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.
Wie Angreifer dies ausnutzen
Das Verstehen von Angriffsmustern hilft Ihnen, bessere Verteidigungen aufzubauen. Dies sind die Techniken, die Sicherheitsteams überwachen.
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.
Wie Sie vorbeugen
- 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
CWEs mit Shoulder-Erkennung (6)
Diese CWEs haben Shoulder-Erkennungsregeln. Klicken Sie, um spezifische Schwachstellen und Korrekturen zu sehen.
Andere zugeordnete CWEs (18)
Diese CWEs sind dieser Kategorie zugeordnet, haben aber noch keine Shoulder-Regeln.