CWE-394 Base Draft

Unexpected Status Code or Return Value

This vulnerability occurs when software fails to properly validate the full range of possible return values from a function or system call. While a returned value might be technically valid for that…

Definition

What is CWE-394?

This vulnerability occurs when software fails to properly validate the full range of possible return values from a function or system call. While a returned value might be technically valid for that operation, the application doesn't anticipate or handle it correctly, leading to unexpected behavior.
Developers often write code expecting only a subset of possible return codes—like success or a few known errors—but overlook other legitimate values the system can produce. This creates a gap where an unexpected but valid return, such as a specific error code from a library update or a rare system state, bypasses the application's logic. Without comprehensive checks, the software might misinterpret the result, proceeding as if the operation succeeded when it actually failed, or vice-versa. To prevent this, implement defensive programming by explicitly handling all documented return values, not just the common ones. Treat any unhandled return as a potential failure and design fallback mechanisms or graceful degradation paths. Always consult the official documentation for functions and APIs to understand the complete spectrum of possible outputs, and write validation logic that accounts for both expected and unexpected-but-valid scenarios to maintain system stability.
Real-world impact

Real-world CVEs caused by CWE-394

  • CVE-2004-1395

    Certain 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-2124

    Unchecked return code from recv() leads to infinite loop.

  • CVE-2005-2553

    Kernel 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-1858

    Memory not properly cleared when read() function call returns fewer bytes than expected.

  • CVE-2000-0536

    Bypass access restrictions when connecting from IP whose DNS reverse lookup does not return a hostname.

  • CVE-2001-0910

    Bypass access restrictions when connecting from IP whose DNS reverse lookup does not return a hostname.

  • CVE-2004-2371

    Game server doesn't check return values for functions that handle text strings and associated size values.

  • CVE-2005-1267

    Resultant infinite loop when function call returns -1 value.

How attackers exploit it

Step-by-step attacker path

  1. 1

    Identify a code path that handles untrusted input without validation.

  2. 2

    Craft a payload that exercises the unsafe behavior — injection, traversal, overflow, or logic abuse.

  3. 3

    Deliver the payload through a normal request and observe the application's reaction.

  4. 4

    Iterate until the response leaks data, executes attacker code, or escalates privileges.

Vulnerable code example

Vulnerable pseudo

MITRE has not published a code example for this CWE. The pattern below is illustrative — see Resources for canonical references.

Vulnerable pseudo 
// Example pattern — see MITRE for the canonical references.
function handleRequest(input) {
  // Untrusted input flows directly into the sensitive sink.
  return executeUnsafe(input);
}
Secure code example

Secure pseudo

Secure pseudo 
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
  const safe = validateAndEscape(input);
  return executeWithGuards(safe);
}
What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Prevention checklist

How to prevent CWE-394

  • Architecture Use safe-by-default frameworks and APIs that prevent the unsafe pattern from being expressible.
  • Implementation Validate input at trust boundaries; use allowlists, not denylists.
  • Implementation Apply the principle of least privilege to credentials, file paths, and runtime permissions.
  • Testing Cover this weakness in CI: SAST rules + targeted unit tests for the data flow.
  • Operation Monitor logs for the runtime signals listed in the next section.
Detection signals

How to detect CWE-394

SAST High

Run static analysis (SAST) on the codebase looking for the unsafe pattern in the data flow.

DAST Moderate

Run dynamic application security testing against the live endpoint.

Runtime Moderate

Watch runtime logs for unusual exception traces, malformed input, or authorization bypass attempts.

Code review Moderate

Code review: flag any new code that handles input from this surface without using the validated framework helpers.

Plexicus auto-fix

Plexicus auto-detects CWE-394 and opens a fix PR in under 60 seconds.

Codex Remedium scans every commit, identifies this exact weakness, and ships a reviewer-ready pull request with the patch. No tickets. No hand-offs.

Get a demo Try Plexicus free
Frequently asked questions

Frequently asked questions

What is CWE-394?

This vulnerability occurs when software fails to properly validate the full range of possible return values from a function or system call. While a returned value might be technically valid for that operation, the application doesn't anticipate or handle it correctly, leading to unexpected behavior.

How serious is CWE-394?

MITRE has not published a likelihood-of-exploit rating for this weakness. Treat it as medium-impact until your threat model proves otherwise.

What languages or platforms are affected by CWE-394?

MITRE has not specified affected platforms for this CWE — it can apply across most application stacks.

How can I prevent CWE-394?

Use safe-by-default frameworks, validate untrusted input at trust boundaries, and apply the principle of least privilege. Cover the data-flow signature in CI with SAST.

How does Plexicus detect and fix CWE-394?

Plexicus's SAST engine matches the data-flow signature for CWE-394 on every commit. When a match is found, our Codex Remedium agent opens a fix PR with the corrected code, tests, and a one-line summary for the reviewer.

Where can I learn more about CWE-394?

MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/394.html. You can also reference OWASP and NIST documentation for adjacent guidance.

Related weaknesses

Weaknesses related to CWE-394

CWE-754 Parent

Improper Check for Unusual or Exceptional Conditions

This weakness occurs when software fails to properly anticipate and handle rare or unexpected runtime situations that fall outside normal…

CWE-252 Sibling

Unchecked Return Value

This vulnerability occurs when a program fails to verify the result of a function or method call, allowing it to continue execution…

CWE-253 Sibling

Incorrect Check of Function Return Value

This vulnerability occurs when a program misinterprets or improperly validates the return value from a function, causing it to miss…

CWE-273 Sibling

Improper Check for Dropped Privileges

This vulnerability occurs when an application tries to lower its system privileges but fails to verify that the operation was successful.

CWE-354 Sibling

Improper Validation of Integrity Check Value

This vulnerability occurs when software fails to properly check the integrity of data by validating its checksum or hash value. Without…

CWE-391 Sibling

Unchecked Error Condition

This vulnerability occurs when a program fails to properly check or handle error conditions, such as exceptions or return codes. By…

CWE-476 Sibling

NULL Pointer Dereference

This vulnerability occurs when a program attempts to access or manipulate memory using a pointer that is set to NULL, causing a crash or…

Resources

Further reading

Ready when you are

Don't Let Security
Weigh You Down.

Stop choosing between AI velocity and security debt. Plexicus is the only platform that runs Vibe Coding Security and ASPM in parallel — one workflow, every codebase.