The product encounters an error but does not provide a status code or return value to indicate that an error has occurred.

Primary

Resultant

Implementation

Integrity
Other
Varies by Context
Unexpected State
Errors that are not properly reported could place the system in an unexpected state that could lead to unintended behaviors.

In the following snippet from a doPost() servlet method, the server returns "200 OK" (default) even if an error occurs.

try {

// Something that may throw an exception.
...
} catch (Throwable t) {logger.error("Caught: " + t.toString());return;}

[REF-1374]
Chain: JavaScript-based cryptocurrency library can fall back to the insecure Math.random() function instead of reporting a failure (CWE-392), thus reducing the entropy (CWE-332) and leading to generation of non-unique cryptographic keys for Bitcoin wallets (CWE-1391)
https://www.unciphered.com/blog/randstorm-you-cant-patch-a-house-of-cards

CVE-2004-0063
Function returns "OK" even if another function returns a different status code than expected, leading to accepting an invalid PIN number.
https://www.cve.org/CVERecord?id=CVE-2004-0063

CVE-2002-1446
Error checking routine in PKCS#11 library returns "OK" status even when invalid signature is detected, allowing spoofed messages.
https://www.cve.org/CVERecord?id=CVE-2002-1446

CVE-2002-0499
Kernel function truncates long pathnames without generating an error, leading to operation on wrong directory.
https://www.cve.org/CVERecord?id=CVE-2002-0499

CVE-2005-2459
Function returns non-error value when a particular erroneous condition is encountered, leading to resultant NULL dereference.
https://www.cve.org/CVERecord?id=CVE-2005-2459

Missing Error Status Code

TPS03-J
Ensure that tasks executing in a thread pool do not fail silently

SFP6
Incorrect Exception Behavior

Allowed
This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.

PLOVER
2006-07-19
Draft 3
2006-07-19

Sean Eidemiller
Cigital
2008-07-01
added/updated demonstrative examples

Eric Dalci
Cigital
2008-07-01
updated Time_of_Introduction

CWE Content Team
MITRE
2008-09-08
updated Relationships, Other_Notes, Taxonomy_Mappings

CWE Content Team
MITRE
2009-03-10
updated Relationships

CWE Content Team
MITRE
2009-10-29
updated Other_Notes, Weakness_Ordinalities

CWE Content Team
MITRE
2010-12-13
updated Description, Name

CWE Content Team
MITRE
2011-06-01
updated Common_Consequences, Relationships, Taxonomy_Mappings

CWE Content Team
MITRE
2011-06-27
updated Common_Consequences

CWE Content Team
MITRE
2012-05-11
updated Common_Consequences, Relationships

CWE Content Team
MITRE
2014-07-30
updated Relationships, Taxonomy_Mappings

CWE Content Team
MITRE
2017-11-08
updated Applicable_Platforms, Modes_of_Introduction, Relationships

CWE Content Team
MITRE
2019-01-03
updated Relationships, Taxonomy_Mappings

CWE Content Team
MITRE
2020-08-20
updated Relationships

CWE Content Team
MITRE
2020-12-10
updated Relationships

CWE Content Team
MITRE
2023-01-31
updated Description

CWE Content Team
MITRE
2023-04-27
updated Modes_of_Introduction, Relationships, Time_of_Introduction

CWE Content Team
MITRE
2023-06-29
updated Mapping_Notes, Relationships

CWE Content Team
MITRE
2023-10-26
updated Demonstrative_Examples

CWE Content Team
MITRE
2024-02-29
4.14
2024-02-29
updated Observed_Examples, References

CWE Content Team
MITRE
2025-04-03
4.17
2025-04-03
updated Relationships

CWE Content Team
MITRE
2025-09-09
4.18
2025-09-09
updated References

Missing Error Status Code
Failure to Report Error in Status Code