CWE-394: Unexpected Status Code or Return Value | Codefreex Skip to content

Security weakness

CWE-394 Unexpected Status Code or Return Value

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-394?

Unexpected Status Code or Return Value: The product does not properly check when a function or operation returns a value that is legitimate for the function, but is not expected by the product.

Business impact

What CWE-394 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-394 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-394

Unexpected Status Code or Return Value

The product does not properly check when a function or operation returns a value that is legitimate for the function, but is not expected by the product.

Weakness ID
CWE-394
Type
Base
Status
Draft
Introduced during
Implementation

Detection and evidence

How CWE-394 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-2004-1395Certain packets (zero byte and other lengths) cause a recvfrom call to produce an unexpected return code that causes a server’s listening loop to exit.
  • CVE-2002-2124Unchecked return code from recv() leads to infinite loop.
  • CVE-2005-2553Kernel function does not properly handle when a null is returned by a function call, causing it to call another function that it shouldn’t.
  • CVE-2005-1858Memory not properly cleared when read() function call returns fewer bytes than expected.
  • CVE-2000-0536Bypass access restrictions when connecting from IP whose DNS reverse lookup does not return a hostname.
  • CVE-2001-0910Bypass access restrictions when connecting from IP whose DNS reverse lookup does not return a hostname.

How we fix it

From finding to fixed: how Codefreex closes CWE-394

  1. 01

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

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

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

    Keep it fixed

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

Related weaknesses

FAQ

CWE-394: FAQs

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

What is CWE-394?

CWE-394, “Unexpected Status Code or Return Value”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. The product does not properly check when a function or operation returns a value that is legitimate for the function, but is not expected by the product.

How serious is CWE-394?

It can affect integrity, other, with impacts such as unexpected state, alter execution logic. The real risk depends on where the weakness sits and what data or functions it exposes.

Can Codefreex check my site for CWE-394?

Yes. A senior engineer reviews your site, store or app for CWE-394 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-394 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.