CWE-390 — Detection of Error Condition Without Action
CWE-390: Detection of Error Condition Without Action
MITRE CWE weakness
| Kind | Weakness |
| Abstraction | Base |
| Status | Draft |
| Likelihood of exploit | Medium |
Description
The product detects a specific error, but takes no actions to handle the error.
Common consequences
- Integrity, Other: Varies by Context, Unexpected State, Alter Execution Logic
Mitigations
Implementation — Properly handle each exception. This is the recommended solution. Ensure that all exceptions are handled in such a way that you can be sure of the state of your system at any given moment.
Implementation — If a function returns an error, it is important to either fix the problem and try again, alert the user that an error has happened and let the program continue, or alert the user and close and cleanup the program.
Testing — Subject the product to extensive testing to discover some of the possible instances of where/how errors or return values are not handled. Consider testing techniques such as ad hoc, equivalence partitioning, robustness and fault tolerance, mutation, and fuzzing.
References
- CWE page: https://cwe.mitre.org/data/definitions/390.html
- CWE list: https://cwe.mitre.org/data/index.html