CWE · MITRE source
CWE-754Improper Check for Unusual or Exceptional Conditions
The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product.
The programmer may assume that certain events or conditions will never occur or do not need to be worried about, such as low memory conditions, lack of access to resources due to restrictive permissions, or misbehaving clients or components. However, attackers may intentionally trigger these unusual conditions, thus violating the programmer's assumptions, possibly introducing instability, incorrect behavior, or a vulnerability. Note that this entry is not exclusively about the use of exceptions and exception handling, which are mechanisms for both checking and handling unusual or unexpected conditions.
Last updated: 09 May 2026 03:25 UTC
NIST 800-53 r5 controls that address this weakness (9)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
CP-12 | Safe Mode | CP | Implements detection of unusual or exceptional conditions followed by safe mode entry, reducing the window for exploitation of unchecked conditions. |
CP-3 | Contingency Training | CP | Training ensures users perform required checks for unusual or exceptional conditions as part of contingency roles, limiting attacker leverage from skipped validations. |
SI-13 | Predictable Failure Prevention | SI | MTTF determination forces explicit checks for conditions that precede predictable component failure. |
SI-6 | Security and Privacy Function Verification | SI | Anomaly detection and alerting implement checks for unusual conditions that would otherwise go unnoticed. |
AU-5 | Response to Audit Logging Process Failures | AU | Requires detection and response to audit logging failures as an unusual or exceptional condition. |
IR-3 | Incident Response Testing | IR | IR testing directly validates checks for unusual or exceptional conditions that could indicate security incidents. |
PM-31 | Continuous Monitoring Strategy | PM | Requires ongoing monitoring of organization-defined metrics and analysis, enabling checks for unusual or exceptional conditions. |
SA-11 | Developer Testing and Evaluation | SA | Security testing routinely checks for unusual or exceptional inputs/conditions, identifying missing validation steps that flaw remediation then resolves. |
SC-24 | Fail in Known State | SC | Requires detection of unusual conditions followed by a controlled transition to the defined failure state. |
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2024-3393 KEV | 8.2 | 7.5 | 0.7769 | 2024-12-27 |
CVE-2024-43044 | 5.7 | 8.8 | 0.6590 | 2024-08-07 |
CVE-2023-41993 KEV | 5.2 | 8.8 | 0.2417 | 2023-09-21 |
CVE-2021-3560 KEV | 4.1 | 7.8 | 0.0955 | 2022-02-16 |
CVE-2017-11144 | 3.9 | 7.5 | 0.4070 | 2017-07-10 |
CVE-2024-4367 | 3.8 | 8.8 | 0.3461 | 2024-05-14 |
CVE-2023-41992 KEV | 3.6 | 7.8 | 0.0106 | 2023-09-21 |
CVE-2018-7287 | 3.2 | 5.9 | 0.3311 | 2018-02-22 |
CVE-2022-20130 | 2.9 | 9.8 | 0.1609 | 2022-06-15 |
CVE-2020-16125 | 2.8 | 7.2 | 0.2210 | 2020-11-10 |
CVE-2020-28037 | 2.7 | 9.8 | 0.1273 | 2020-11-02 |
CVE-2019-19646 | 2.5 | 9.8 | 0.0946 | 2019-12-09 |
CVE-2024-52316 | 2.1 | 9.8 | 0.0267 | 2024-11-18 |
CVE-2019-0036 | 2.0 | 9.8 | 0.0026 | 2019-04-10 |
CVE-2019-15900 | 2.0 | 9.8 | 0.0035 | 2019-10-18 |
CVE-2020-10571 | 2.0 | 9.8 | 0.0042 | 2020-03-14 |
CVE-2020-8986 | 2.0 | 9.8 | 0.0092 | 2020-03-24 |
CVE-2021-0211 | 2.0 | 10.0 | 0.0039 | 2021-01-15 |
CVE-2021-33622 | 2.0 | 9.8 | 0.0055 | 2021-06-15 |
CVE-2017-20166 | 2.0 | 9.8 | 0.0060 | 2023-01-10 |
CVE-2023-37303 | 2.0 | 9.8 | 0.0024 | 2023-06-30 |
CVE-2024-3729 | 2.0 | 9.8 | 0.0055 | 2024-05-02 |
CVE-2024-7826 | 2.0 | 9.8 | 0.0030 | 2024-10-03 |
CVE-2026-24054 | 2.0 | 10.0 | 0.0009 | 2026-01-29 |
CVE-2026-4689 | 2.0 | 10.0 | 0.0003 | 2026-03-24 |