CWE-392: Missing Report of Error Condition
Official CWE-392 CWE context with Glexia analysis, remediation guidance, related CVEs, and ATT&CK context.
Glexia's Take
CWE-392: Missing Report of Error Condition
Missing Report of Error Condition represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Executive Impact
- Integrity,Other: Varies by Context,Unexpected State: Errors that are not properly reported could place the system in an unexpected state that could lead to unintended behaviors.
Developer Pattern
CWE-392 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.
Confidence
high confidence from CWE-392, 4.20.
Official CWE Definition
CWE-392: Missing Report of Error Condition
The product encounters an error but does not provide a status code or return value to indicate that an error has occurred.
Developer And Remediation Guidance
How teams prevent and detect this weakness
Causes
- In the following snippet from a doPost() servlet method, the server returns "200 OK" (default) even if an error occurs.
Remediation
- Use safe APIs
- Centralize the control
- Add regression tests
- Review logs and telemetry for attempted abuse
Detection
- Code review
- SAST
- DAST
- Focused regression tests
Mappings
Related CVEs, CWEs, and ATT&CK context
Related CWEs
- CWE-1429: Missing Security-Relevant Feedback for Unexecuted Operations in Hardware Interface
- CWE-684: Incorrect Provision of Specified Functionality
- CWE-703: Improper Check or Handling of Exceptional Conditions
- CWE-703: Improper Check or Handling of Exceptional Conditions
- CWE-755: Improper Handling of Exceptional Conditions
ATT&CK Relevance
ATT&CK relevance is shown only when reviewed or responsibly inferred.