Skip to content
OpenAdvisories

Weakness (CWE)

CWE-390: Detection of Error Condition Without Action

Base Draft

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

How to prevent it (3 mitigations)
  1. 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.

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

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

  • Medium 6.8
    CVE-2025-26465 Public exploit

    Openssh: machine-in-the-middle attack if verifyhostkeydns is enabled

    A vulnerability was found in OpenSSH when the VerifyHostKeyDNS option is enabled. A machine-in-the-middle attack can be performed by a malicious machine impersonating a legit server. This issue occurs due to how OpenSSH mishandles error codes in specific cond…

  • Medium 5.3
    CVE-2024-30255 Public exploit EPSS 85%

    HTTP/2: CPU exhaustion due to CONTINUATION frame flood

    Envoy is a cloud-native, open source edge and service proxy. The HTTP/2 protocol stack in Envoy versions prior to 1.29.3, 1.28.2, 1.27.4, and 1.26.8 are vulnerable to CPU exhaustion due to flood of CONTINUATION frames. Envoy's HTTP/2 codec allows the client t…