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-2026-22795 Missing ASN1_TYPE validation in PKCS#12 parsing — OpenSSL 7.5AIHighAI2026-01-27
CVE-2025-69420 Missing ASN1_TYPE validation in TS_RESP_verify_response() function — OpenSSL 6.2AIMediumAI2026-01-27
CVE-2025-12387 Denial of Service in Pix-Link LV-WR21Q — LV-WR21Q 7.5AIHighAI2026-01-27
CVE-2026-21910 Junos OS: EX4k Series, QFX5k Series: In an EVPN-VXLAN configuration link flaps cause Inter-VNI traffic drop — Junos OS 6.5 Medium2026-01-15
CVE-2025-60011 Junos OS and Junos OS Evolved: Optional transitive BGP attribute is modified before propagation to peers causing sessions to flap — Junos OS 5.8 Medium2026-01-15
CVE-2025-59960 Junos OS and Junos OS Evolved: DHCP Option 82 messages from clients being passed unmodified to the DHCP server — Junos OS 7.4 High2026-01-15
CVE-2026-0227 PAN-OS: Firewall Denial of Service (DoS) in GlobalProtect Gateway and Portal — Cloud NGFW 7.5AIHighAI2026-01-15
CVE-2025-4675 Improper implementation of Modbus protocol leading to DOS attack — WebPro SNMP Card PowerValue 6.5 Medium2026-01-07
CVE-2025-20761 MediaTek chipsets 安全漏洞 — MediaTek chipset 7.5 -2026-01-06
CVE-2025-66357 Inaba Denki Sangyo CHOCO TEI WATCHER mini 代码问题漏洞 — CHOCO TEI WATCHER mini (IB-MCT001) 7.5AIHighAI2025-12-16
CVE-2025-61976 Inaba Denki Sangyo CHOCO TEI WATCHER mini 代码问题漏洞 — CHOCO TEI WATCHER mini (IB-MCT001) 7.5AIHighAI2025-12-16
CVE-2025-33201 NVIDIA Triton Inference Server 代码问题漏洞 — Triton Inference Server 7.5 High2025-12-03
CVE-2025-64704 WebAssembly Micro Runtime vulnerable to a segmentation fault in v128.store instruction — wasm-micro-runtime 4.7 Medium2025-11-25
CVE-2025-62875 Local DoS in OpenSMTPD via UNIX domain socket smtpd.sock — openSUSE Tumbleweed 5.5 -2025-11-20
CVE-2025-13080 Drupal core - Moderately critical - Denial of Service - SA-CORE-2025-005 — Drupal core--AI2025-11-18
CVE-2025-64342 ESF-IDF's ESP32 Bluetooth Controller Has an Invalid Access Address Vulnerability — esp-idf--AI2025-11-17
CVE-2025-4619 PAN-OS: Firewall Denial of Service (DoS) Using Specially Crafted Packets — Cloud NGFW 7.5 -2025-11-13
CVE-2025-12657 Malformed KMIP response may result in access violation — MongoDB Server 5.0 Medium2025-11-03
CVE-2025-10937 Oxford Nanopore Technologies MinKNOW Improper Check for Unusual or Exceptional Conditions — MinKNOW 5.5 Medium2025-10-23
CVE-2025-62605 Mastodon quotes control can be bypassed — mastodon 4.3 Medium2025-10-21
CVE-2025-11925 Incorrect Content-Type Header — BLU-IC2 6.1AIMediumAI2025-10-17
CVE-2025-55035 Mattermost Desktop DoS when user has basic authentication server configured — Mattermost 6.1 Medium2025-10-16
CVE-2024-26008 Fortinet多款产品 代码问题漏洞 — FortiProxy 5.0 Medium2025-10-14
CVE-2025-60004 Junos OS and Junos OS Evolved: Specific BGP EVPN update message causes rpd crash — Junos OS 7.5 High2025-10-09
CVE-2025-59958 Junos OS Evolved: PTX Series: When a firewall filter rejects traffic these packets are erroneously sent to the RE — Junos OS Evolved 6.5 Medium2025-10-09
CVE-2025-58354 Kata Containers coco-tdx malicious host can circumvent initdata verification — kata-containers 8.8AIHighAI2025-09-23
CVE-2025-8716 Cache exploitation vulnerability — OpenText Content Management 6.5AIMediumAI2025-09-11
CVE-2025-9998 Improper validation of packets sequencing — PcVue 7.5AIHighAI2025-09-05
CVE-2025-24975 Firebird Non-Authorized Access to Encrypted Database Using Execute Statement on External — firebird 7.1 High2025-08-15
CVE-2024-52504 Siemens多款产品 代码问题漏洞 — SIPROTEC 4 6MD61 7.5 High2025-08-12

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