CWE-390: Detection of Error Condition Without Action
BaseLikelihood of exploit: Medium
The product detects a specific error, but takes no actions to handle the error.
Consequences
- Integrity, Other: Varies by Context, Unexpected State, Alter Execution Logic
How to prevent it
- 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.
Recent advisories
- GHSA-fj9w-c36g-h5x8 — AsyncHttpClient doesn't verify SCRAM and Digest mutual-authentication responses
- DRUPAL-CORE-2024-002 — Drupal core vulnerable to improper error handling
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor