Detection of Error Condition Without Action

Opis

The product detects a specific error, but takes no actions to handle the error.

Skutki

• Integrity, Other

  Varies by Context; Unexpected State; Alter Execution Logic

  An attacker could utilize an ignored error condition to place the system in an unexpected state that could lead to the execution of unintended logic and could cause other unintended behavior.

Zapobieganie

• 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.

Przykłady podatności

• CVE-2022-21820 A GPU data center manager detects an error due to a malformed request but does not act on it, leading to memory corruption.

Słabość nadrzędna

• CWE-755 Improper Handling of Exceptional Conditions

Może prowadzić do

• CWE-401 Missing Release of Memory after Effective Lifetime

Kiedy powstaje

• Implementation — REALIZATION: This weakness is caused during implementation of an architectural security tactic.

Dotyczy

Not Language-Specific

Źródła

1. The CLASP Application Security Process — Secure Software, Inc., 2005
2. 24 Deadly Sins of Software Security — Michael Howard, David LeBlanc, John Viega, "Sin 11: Failure to Handle Errors Correctly." Page 183, McGraw-Hill, 2010