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

Primary

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

Medium

Integrity
Other
Varies by Context
Unexpected State
Alter Execution Logic
An 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.

Automated Static Analysis
Automated 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

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.

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

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.

The following example attempts to allocate memory for a character. After the call to malloc, an if statement is used to check whether the malloc function failed.

foo=malloc(sizeof(char)); //the next line checks to see if malloc failedif (foo==NULL) {//We do nothing so we just ignore the error.}

The conditional successfully detects a NULL return value from malloc indicating a failure, however it does not do anything to handle the problem. Unhandled errors may have unexpected results and may cause the program to crash or terminate.
Instead, the if block should contain statements that either attempt to fix the problem or notify the user that an error has occurred and continue processing or perform some cleanup and gracefully terminate the program. The following example notifies the user that the malloc function did not allocate the required memory resources and returns an error code.

foo=malloc(sizeof(char)); //the next line checks to see if malloc failedif (foo==NULL) {printf("Malloc failed to allocate memory resources");return -1;}

In the following C++ example the method readFile() will read the file whose name is provided in the input parameter and will return the contents of the file in char string. The method calls open() and read() may result in errors if the file does not exist or does not contain any data to read. These errors will be thrown when the is_open() method and good() method indicate errors opening or reading the file. However, these errors are not handled within the catch statement. Catch statements that do not perform any processing will have unexpected results. In this case an empty char string will be returned, and the file will not be properly closed.

char* readfile (char *filename) {
try {
// open input fileifstream infile;infile.open(filename);
if (!infile.is_open()) {throw "Unable to open file " + filename;}
// get length of fileinfile.seekg (0, ios::end);int length = infile.tellg();infile.seekg (0, ios::beg);
// allocate memorychar *buffer = new char [length];
// read data from fileinfile.read (buffer,length);
if (!infile.good()) {throw "Unable to read from file " + filename;}
infile.close();
return buffer;
}catch (...) {/* bug: insert code to handle this later */}
}

The catch statement should contain statements that either attempt to fix the problem or notify the user that an error has occurred and continue processing or perform some cleanup and gracefully terminate the program. The following C++ example contains two catch statements. The first of these will catch a specific error thrown within the try block, and the second catch statement will catch all other errors from within the catch block. Both catch statements will notify the user that an error has occurred, close the file, and rethrow to the block that called the readFile() method for further handling or possible termination of the program.

char* readFile (char *filename) {
try {
// open input fileifstream infile;infile.open(filename);
if (!infile.is_open()) {throw "Unable to open file " + filename;}
// get length of fileinfile.seekg (0, ios::end);int length = infile.tellg();infile.seekg (0, ios::beg);
// allocate memorychar *buffer = new char [length];
// read data from fileinfile.read (buffer,length);
if (!infile.good()) {throw "Unable to read from file " + filename;}infile.close();
return buffer;
}catch (char *str) {printf("Error: %s \n", str);infile.close();throw str;}catch (...) {printf("Error occurred trying to read from file \n");infile.close();throw;}
}

In the following Java example the method readFile will read the file whose name is provided in the input parameter and will return the contents of the file in a String object. The constructor of the FileReader object and the read method call may throw exceptions and therefore must be within a try/catch block. While the catch statement in this example will catch thrown exceptions in order for the method to compile, no processing is performed to handle the thrown exceptions. Catch statements that do not perform any processing will have unexpected results. In this case, this will result in the return of a null String.

public String readFile(String filename) {
String retString = null;try {
// initialize File and FileReader objectsFile file = new File(filename);FileReader fr = new FileReader(file);
// initialize character bufferlong fLen = file.length();char[] cBuf = new char[(int) fLen];
// read data from fileint iRead = fr.read(cBuf, 0, (int) fLen);
// close filefr.close();
retString = new String(cBuf);

} catch (Exception ex) {/* do nothing, but catch so it'll compile... */}return retString;
}

The catch statement should contain statements that either attempt to fix the problem, notify the user that an exception has been raised and continue processing, or perform some cleanup and gracefully terminate the program. The following Java example contains three catch statements. The first of these will catch the FileNotFoundException that may be thrown by the FileReader constructor called within the try/catch block. The second catch statement will catch the IOException that may be thrown by the read method called within the try/catch block. The third catch statement will catch all other exceptions thrown within the try block. For all catch statements the user is notified that the exception has been thrown and the exception is rethrown to the block that called the readFile() method for further processing or possible termination of the program. Note that with Java it is usually good practice to use the getMessage() method of the exception class to provide more information to the user about the exception raised.

public String readFile(String filename) throws FileNotFoundException, IOException, Exception {
String retString = null;try {
// initialize File and FileReader objectsFile file = new File(filename);FileReader fr = new FileReader(file);
// initialize character bufferlong fLen = file.length();char [] cBuf = new char[(int) fLen];
// read data from fileint iRead = fr.read(cBuf, 0, (int) fLen);
// close filefr.close();
retString = new String(cBuf);

} catch (FileNotFoundException ex) {System.err.println ("Error: FileNotFoundException opening the input file: " + filename );System.err.println ("" + ex.getMessage() );throw new FileNotFoundException(ex.getMessage());} catch (IOException ex) {System.err.println("Error: IOException reading the input file.\n" + ex.getMessage() );throw new IOException(ex);} catch (Exception ex) {System.err.println("Error: Exception reading the input file.\n" + ex.getMessage() );throw new Exception(ex);}return retString;
}

CVE-2022-21820
A GPU data center manager detects an error due to a malformed request but does not act on it, leading to memory corruption.
https://www.cve.org/CVERecord?id=CVE-2022-21820

Improper error handling

ERR00-J
Do not suppress or ignore checked exceptions

SFP4
Unchecked Status Condition

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.

CLASP
2006-07-19
Draft 3
2006-07-19

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
2008-11-24
updated Demonstrative_Examples, Description, Other_Notes, Potential_Mitigations

CWE Content Team
MITRE
2009-03-10
updated Relationships

CWE Content Team
MITRE
2009-07-27
updated Demonstrative_Examples

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
2011-09-13
updated Relationships, Taxonomy_Mappings

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

CWE Content Team
MITRE
2014-02-18
updated Related_Attack_Patterns

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, Taxonomy_Mappings

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

CWE Content Team
MITRE
2020-02-24
updated References, Type

CWE Content Team
MITRE
2020-08-20
updated Relationships

CWE Content Team
MITRE
2023-01-31
updated Description, Potential_Mitigations

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

CWE Content Team
MITRE
2023-06-29
updated Mapping_Notes

CWE Content Team
MITRE
2023-10-26
updated Observed_Examples

CWE Content Team
MITRE
2024-02-29
4.14
2024-02-29
updated Demonstrative_Examples

CWE Content Team
MITRE
2025-12-11
4.19
2025-12-11
updated Relationships, Weakness_Ordinalities

Improper Error Handling