CWE-390: Detection of Error Condition Without Action

What is CWE-390?

CWE-390 is Detection of Error Condition Without Action. The flaw arises when the product detects a specific error, but takes no actions to handle the error. The database currently holds 16 vulnerabilities mapped to CWE-390 and none of them are in the CISA Known Exploited Vulnerabilities catalog.

OWASP TOP 10:2025 RANK10 — A10:2025 — Mishandling of Exceptional Conditions
Related CVES (365 days)16
AbstractionBase
Likelihood of exploitMedium

Vulnerabilities mapped to CWE-390

16 vulnerabilities167% increase year over year

No data

No vulnerability data in CISA KEV for CWE-390

Official definition

ByMitre CWE

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

Characteristics

Modes of introduction

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

Common consequences

ImpactScopeExplanation
Varies by Context, Unexpected State, Alter Execution LogicIntegrity, OtherAn 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.

Risk mitigations

  1. ImplementationProperly 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. ImplementationIf 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. TestingSubject 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.

Detection methods

MethodApproachEffectiveness
Automated Static AnalysisAutomated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)High

Representative vulnerabilities

Sources (2)

CWE™ Program, operated by The MITRE Corporation. Copyright © 2006–2026, The MITRE Corporation. The MITRE Corporation hereby grants you a non-exclusive, royalty-free license to use CWE for research, development, and commercial purposes. CWE Terms of Use.

Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.