Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-754 (对因果或异常条件的不恰当检查) — Vulnerability Class 272

272 vulnerabilities classified as CWE-754 (对因果或异常条件的不恰当检查). AI Chinese analysis included.

CWE-754 represents a critical software weakness where applications fail to properly validate or handle unexpected environmental states, such as resource exhaustion, permission denials, or malformed inputs. Developers often exploit this oversight by assuming routine operational conditions will always hold true, leading to crashes, data corruption, or security breaches when rare events occur. Attackers typically trigger these exceptional conditions to cause denial-of-service attacks or to bypass security controls by forcing the application into an undefined state. To mitigate this risk, engineers must implement robust error handling mechanisms that explicitly check for and gracefully manage unusual scenarios. This includes validating resource availability, verifying user permissions, and ensuring inputs meet expected formats before processing, thereby maintaining system stability and security even under adverse or unexpected operating conditions.

MITRE CWE Description
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.
Common Consequences (1)
Integrity, AvailabilityDoS: Crash, Exit, or Restart, Unexpected State
The data which were produced as a result of a function call could be in a bad state upon return. If the return value is not checked, then this bad data may be used in operations, possibly leading to a crash or other unintended behaviors.
Mitigations (5)
RequirementsUse a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Choose languages with features such as exception handling that force the programmer to anticipate unusual conditions that may generate exceptions. Custom exceptions may need to be developed to handle unusual business-logic conditions. Be careful not to pass sensitive exceptions…
ImplementationCheck the results of all functions that return a value and verify that the value is expected.
Effectiveness: High
ImplementationIf using exception handling, catch and throw specific exceptions instead of overly-general exceptions (CWE-396, CWE-397). Catch and handle exceptions as locally as possible so that exceptions do not propagate too far up the call stack (CWE-705). Avoid unchecked or uncaught exceptions where feasible (CWE-248).
Effectiveness: High
ImplementationEnsure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or…
ImplementationAssume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range…
Examples (2)
Consider the following code segment:
char buf[10], cp_buf[10]; fgets(buf, 10, stdin); strcpy(cp_buf, buf);
Bad · C
The following code does not check to see if memory allocation succeeded before attempting to use the pointer returned by malloc().
buf = (char*) malloc(req_size); strncpy(buf, xfer, req_size);
Bad · C
CVE IDTitleCVSSSeverityPublished
CVE-2025-30258 GnuPG 安全漏洞 — GnuPG 2.7 Low2025-03-19
CVE-2025-0116 PAN-OS: Firewall Denial of Service (DoS) Using a Specially Crafted LLDP Frame — PAN-OS 6.5 -2025-03-12
CVE-2024-54175 IBM MQ denial of service — MQ 5.5 Medium2025-02-28
CVE-2025-0112 Cortex XDR Agent: Local Windows User Can Disable the Agent — Cortex XDR Agent 7.8 -2025-02-19
CVE-2025-0503 Leaked User IDs and Metadata of Deleted DMs — Mattermost 3.1 Low2025-02-14
CVE-2024-52895 IBM i denial of service — i 6.5 Medium2025-02-14
CVE-2024-45650 IBM Security Verify Directory denial of service — Security Verify Directory 7.5 High2025-01-31
CVE-2025-23197 matrix-hookshot has a Potential Denial of Service when Hookshot is configured with GitHub support — matrix-hookshot 6.5 Medium2025-01-27
CVE-2024-29980 Unsafe Handling of IHV UEFI Variables — SecureCore™ for Intel Kaby Lake 2.3 Low2025-01-14
CVE-2024-29979 Unsafe Handling of Phoenix UEFI Variables — SecureCore™ for Intel Kaby Lake 2.3 Low2025-01-14
CVE-2025-22445 Misleading UI for undefined admin console settings in Calls causes security confusion — Mattermost 3.5 Low2025-01-09
CVE-2024-3393 PAN-OS: Firewall Denial of Service (DoS) in DNS Security Using a Specially Crafted Packet — Cloud NGFW 7.5 -2024-12-27
CVE-2024-51470 IBM MQ denial of service — MQ 6.5 Medium2024-12-18
CVE-2024-54116 Huawei HarmonyOS 缓冲区错误漏洞 — HarmonyOS 4.3 Medium2024-12-12
CVE-2024-54115 Huawei HarmonyOS 缓冲区错误漏洞 — HarmonyOS 4.3 Medium2024-12-12
CVE-2024-54114 Huawei HarmonyOS 缓冲区错误漏洞 — HarmonyOS 4.4 Medium2024-12-12
CVE-2024-11599 Domain Restriction Bypass on Registration — Mattermost 8.2 High2024-11-28
CVE-2024-10945 FactoryTalk® Updater Local Privilege Escalation — FactoryTalk Updater 7.3 High2024-11-12
CVE-2024-45085 IBM WebSphere Application Server denial of service — WebSphere Application Server 5.9 Medium2024-10-15
CVE-2024-47507 Junos OS and Junos OS Evolved: BGP update message containing aggregator attribute with an ASN value of zero (0) is accepted — Junos OS 5.8 Medium2024-10-11
CVE-2024-47503 Junos OS: SRX4600 and SRX5000 Series: Sequence of specific PIM packets causes a flowd crash — Junos OS 6.5 Medium2024-10-11
CVE-2024-47499 Junos OS and Junos OS Evolved: In a BMP scenario receipt of a malformed AS PATH attribute can cause an RPD crash — Junos OS 7.5 High2024-10-11
CVE-2024-9469 Cortex XDR Agent: Local Windows User Can Disable the Agent — Cortex XDR Agent 7.8AIHighAI2024-10-09
CVE-2024-9124 Rockwell Automation PowerFlex 6000T CIP Security denial-of-service Vulnerability — Drives - PowerFlex 6000T 7.5AIHighAI2024-10-08
CVE-2024-7826 Unhandled exception vulnerability that can cause the WRSA.exe service to crash and generate a crash dump — SecureAnywhere - Web Shield 9.8 -2024-10-03
CVE-2024-8175 CODESYS: web server vulnerable to DoS — CODESYS Control for BeagleBone SL 7.5 High2024-09-25
CVE-2024-2502 Failure to update the tamper reset cause register when a tamper event occurs — SE Firmware 2.0 Low2024-08-29
CVE-2024-42411 User creation date manipulation in POST /api/v4/users — Mattermost 5.3 Medium2024-08-22
CVE-2024-40619 Rockwell Automation GuardLogix/ControlLogix 5580 Controller denial-of-service Vulnerability via Malformed Packet Handling — ControlLogix® 5580 7.5AIHighAI2024-08-14
CVE-2024-39832 Permanently local data deletion by malicious remote — Mattermost 6.8 Medium2024-08-01

Vulnerabilities classified as CWE-754 (对因果或异常条件的不恰当检查) represent 272 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.