CWE-390
Detection of Error Condition Without Action
Description
The product detects a specific error, but takes no actions to handle the error.
Parent Weaknesses (ChildOf)
Related Weaknesses
Common Consequences
Scope
Impact
Varies by Context, Unexpected State, Alter Execution Logic
Potential Mitigations
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.
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.
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.
CVE-2022-21820A GPU data center manager detects an error due to a malformed request but does not act on it, leading to memory corruption.
Applicable Platforms
Security Training
Train your team to recognize and prevent security threats with our comprehensive security awareness program.
Start TrainingVulnerability Scanning
Discover vulnerabilities in your applications and infrastructure before attackers do.
Scan Now