CWE-390: Detection of Error Condition Without Action Skip to content

Security weakness

CWE-390 Detection of Error Condition Without Action

A base-level weakness that can lead to data and pages or code changed. Here is what it is, what it can cost you and how to close it.

  • Senior security engineers
  • 540+ projects delivered
  • Reply within one business day

Quick answer

What is CWE-390?

Detection of Error Condition Without Action: The product detects a specific error, but takes no actions to handle the error.

Business impact

What CWE-390 could cost your business

MITRE documents what this weakness can do. Here is what that means for a website, store or app.

Integrity

Data, pages or code changed

Prices, orders, content or the code your site runs can be altered without your approval.

  • Unexpected State
  • Alter Execution Logic

Free security check

Is CWE-390 hiding in your site?

A senior engineer checks your site, store or app for this weakness and the rest of the CWE Top 25, then sends a prioritized fix plan within one business day. No obligation.

Official definition

How MITRE defines CWE-390

Detection of Error Condition Without Action

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

Weakness ID
CWE-390
Type
Base
Status
Draft
Likelihood of exploit
Medium
Introduced during
Implementation

Prevention

How to fix CWE-390, phase by phase

Every mitigation from the CWE entry, in the order a project runs: plan, build, test, operate.

  1. 01

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

    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.

Detection and evidence

How CWE-390 is found, and where it has hit

The testing methods MITRE recommends, and real vulnerabilities this weakness has caused.

How it is detected

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

Real vulnerabilities it caused

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

How we fix it

From finding to fixed: how Codefreex closes CWE-390

  1. Scan and confirm

    We test your site, store or app for this weakness and the rest of the CWE Top 25 with automated scanning and manual review, and confirm what is actually exploitable.

  2. Fix at the source

    We change the code, configuration or dependency that causes it, not just the symptom, and plan the changes to avoid downtime.

  3. Verify the fix

    We retest every finding, check that nothing else broke and hand you a short report you can share with your team, client or auditor.

  4. Keep it fixed

    Updates, monitoring and maintenance so the weakness does not return with the next plugin, theme, app or code change.

FAQ

CWE-390: FAQs

Short answers for owners and developers. Not sure whether your site is affected? Ask us to check.

What is CWE-390?

CWE-390, “Detection of Error Condition Without Action”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. The product detects a specific error, but takes no actions to handle the error.

How serious is CWE-390?

MITRE rates the likelihood of exploit as Medium. It can affect integrity, other, with impacts such as varies by context, unexpected state, alter execution logic. The real risk depends on where the weakness sits and what data or functions it exposes.

How do you prevent CWE-390?

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

Can Codefreex check my site for CWE-390?

Yes. A senior engineer reviews your site, store or app for CWE-390 and the rest of the CWE Top 25, confirms what is exploitable and sends a prioritized fix plan within one business day. Start with the free security check form on this page.

Free security check

Find out if CWE-390 affects your site

Send your URL. A senior engineer checks for this weakness and the rest of the CWE Top 25, and replies within one business day with what to fix first.

  • A senior strategist reviews your request, not a sales bot
  • Clear scope, timeline and estimate within one business day
  • Free 30-minute discovery call, no obligation
  • NDA available on request

Weakness data from the Common Weakness Enumeration (CWE®) version 5.0, Copyright © 2006–2026, The MITRE Corporation. CWE is free to use by any organization or individual for any research, development, and/or commercial purposes under the CWE Terms of Use. CWE is a registered trademark of The MITRE Corporation. The business impact, risk profile and plain-English guidance on this page are written by Codefreex and are general information, not a security assessment of your system.