Learn about CWE-391, a vulnerability where unchecked exceptions may lead to system instability. Understand the implications and best practices to handle such errors effectively.

CWE-388: Error Handling: Errors in Application Error Management

CWE-728: Vulnerabilities Linked to OWASP Top Ten (2004)

CWE-743: Weaknesses in Input Output (FIO) of CERT C Standard

CWE-746: Weaknesses in Error Handling of CERT C Secure Coding Standard (2008)

CWE-876: Memory Management Vulnerabilities in CERT C++ Secure Coding Standard

CWE-877: Weaknesses in Input Output Section of CERT C++ Standard

CWE-880: Exceptions and Error Handling Weaknesses

CWE-962: Unchecked Status Condition Cluster (SFP4)

CWE-1159: Deficiencies in Floating Point (FLP) Part of SEI CERT C Coding Standard

CWE-1167: Vulnerabilities in Error Handling (ERR) Segment of SEI CERT C Coding Standard

CWE-1171: Deficiencies in POSIX Regulations and Suggestions

CWE-1181: SEI CERT Perl Coding Standard's Expressions Weaknesses

CWE-1405: Inadequate Verification or Management of Atypical Circumstances

Discover how CWE-391 can impact system stability. Find guidance on effectively managing unchecked errors for a robust system. Learn key practices to secure your code.

CWE-391: Unchecked Error Condition - Best Practices for Handling Exceptions

By disregarding an exception, a programmer is essentially indicating that they are working on the basis of either of the following two assumptions:

1. The method call will never encounter an error.
2. The outcome of this call failing is inconsequential.

CWE-391: Unchecked Error Condition

CWE-391: Unchecked Error Condition

Is your System Free of Underlying Vulnerabilities? Find Out Now

Is your System Free of Underlying Vulnerabilities?
Find Out Now