CWE-600: Uncaught Exception in Servlet | Glexia
CWE-600 (Uncaught Exception in Servlet) weakness overview with consequences, detection methods, mitigations, related CVEs and MITRE ATT&CK context.
Glexia's Take · Automated analysis
CWE-600: Missing Catch Block
Uncaught Exception in Servlet represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Executive Impact
- Confidentiality Availability: Read Application Data DoS: Crash, Exit, or Restart
Developer Pattern
CWE-600 is the kind of defect developers can usually prevent with explicit validation, safer framework defaults, and tests that exercise hostile input or unsafe state transitions.
Automation confidence
high confidence from CWE-600, 4.20.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Official CWE Definition
CWE-600: Uncaught Exception in Servlet
The Servlet does not catch all exceptions, which may reveal sensitive debugging information.
When a Servlet throws an exception, the default error response the Servlet container sends back to the user typically includes debugging information. This information is of great value to an attacker. For example, a stack trace might show the attacker a malformed SQL query string, the type of database being used, and the version of the application container. This information enables the attacker to target known vulnerabilities in these components.
Developer And Remediation Guidance
How teams prevent and detect this weakness
Causes
- The following example attempts to resolve a hostname. A DNS lookup failure will cause the Servlet to throw an exception.
Remediation
- Implementation: Implement Exception blocks to handle all types of Exceptions.
Detection
- Code review
- SAST
- DAST
- Focused regression tests
Mappings
Related CVEs, CWEs, and ATT&CK context
Related CWEs
ATT&CK Relevance
ATT&CK relevance is shown only when reviewed or responsibly inferred.