Weakness (CWE)
CWE-390: Detection of Error Condition Without Action
The product detects a specific error, but takes no actions to handle the error.
How to prevent it (3 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.
Source: MITRE CWE-390
2 results · Clear filters · Feed
-
Low 3.7
AsyncHttpClient: SCRAM and Digest mutual-authentication responses are not verified
The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. From 3.0.8 until 3.0.12, processScramAuthenticationInfo and processAuthenticationInfo compute the SCRAM ServerSignature or Di…
-
Low 1.8
Improper handling of error condition during host-induced faults can allow a local high-privileged attack to selectively…