CWE-754Improper Check for Unusual or Exceptional Conditions

Description

Common consequences· 1

• Integrity / Availability — DoS: Crash, Exit, or Restart, Unexpected State
  The data which were produced as a result of a function call could be in a bad state upon return. If the return value is not checked, then this bad data may be used in operations, possibly leading to a crash or other unintended behaviors.

Potential mitigations· 5

• [Requirements]
• [Implementation]Check the results of all functions that return a value and verify that the value is expected.
• [Implementation]If using exception handling, catch and throw specific exceptions instead of overly-general exceptions (CWE-396, CWE-397). Catch and handle exceptions as locally as possible so that exceptions do not propagate too far up the call stack (CWE-705). Avoid unchecked or uncaught exceptions where feasible (CWE-248).
• [Implementation]
• [Implementation]

(incoming)16

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.