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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

367 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, Availability DoS: 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)
Requirements Use 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…
Implementation Check the results of all functions that return a value and verify that the value is expected.
Effectiveness: High
Implementation If 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
Implementation Ensure 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…
Implementation Assume 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 ID Title CVSS Severity Published
CVE-2026-40670 AMD SEV-SNP 异常检查不当致完整性受损 — AMD EPYC™ 9004 Series Processors 5.9 Medium 2026-11-10
CVE-2026-120807 Privilege escalation via fail-open user lookup in X.509 cluster-membership guard — MongoDB Server 6.6 Medium 2026-11-10
CVE-2026-123588 Hickory DNS Recursive Resolver Denial of Service via Cached Empty Connection Pool — hickory-dns 7.5 High 2026-11-08
CVE-2026-48186 AS 安全激活前消息处理不当致异常行为 — Exynos 1280 - - 2026-11-05
CVE-2026-69006 GNSS 固件加载器长度验证不足致内核内存损坏 — Exynos 850 - - 2026-11-05
CVE-2026-69066 GPU 驱动因 VMID 验证不当导致内存破坏 — Exynos 2200 - - 2026-11-05
CVE-2025-66368 SDP 载荷处理不当导致拒绝服务漏洞 — Exynos 1080 - - 2026-11-05
CVE-2026-35495 IMS 堆栈 SIP 包处理不当引发访问控制漏洞 — Exynos 1080 - - 2026-11-05
CVE-2025-66365 SIP 数据包处理不当导致基带崩溃漏洞 — Exynos 1080 - - 2026-11-05
CVE-2025-66364 基带软件:控制面消息持续发送导致崩溃 — Exynos 850 - - 2026-11-05
CVE-2026-121054 Chrome 157.0.8103.38 前 XML 状态验证绕过漏洞 — Chrome - - 2026-11-03
CVE-2026-121237 Chrome 157.0.8103.38 前 FileSystem 状态验证绕过漏洞 — Chrome - - 2026-11-03
CVE-2026-121098 Chrome 157.0.8103.38 GPU 状态验证绕过漏洞 — Chrome - - 2026-11-03
CVE-2026-121445 svg-sanitizer 1.0.0 before 1.1.0 ReDoS and Fail-Open via image-set CSS Stripping — svg-sanitizer 5.9 Medium 2026-11-03
CVE-2026-117680 jsv treats regex match budget exhaustion as a non-match, bypassing patternProperties and not — jsv 2.1 Low 2026-11-01
CVE-2026-62334 OpenVM's OpenVmHalo2Verifier self-call can bypass proof verification — openvm 8.7 High 2026-10-30
CVE-2026-107311 Permissions by Term - Moderately critical - Information disclosure - SA-CONTRIB-2026-214 — Permissions by Term - - 2026-10-30
CVE-2026-62374 SD JWT JS: Tampered disclosures silently dropped instead of rejected — @sd-jwt/core 7.1 High 2026-10-29
CVE-2026-119126 Parse Server before 8.6.106 and 9.0.0 before 9.10.5-alpha.7 afterSave Trigger and LiveQuery Bypass via Dot Notation Keys — parse-server 3.1 Low 2026-10-29
CVE-2026-116516 Insufficient length validation when parsing Zoom chat transcriptions — Mattermost 6.5 Medium 2026-10-26
CVE-2026-115385 Wasmtime 46.0.0 before 48.0.4 and 49.0.0 before 49.0.2 Host Panic via WASIp3 Timestamps — wasmtime 6.2 Medium 2026-10-22
CVE-2026-13411 Null condition in Playbooks import crashes the plugin — Mattermost 4.3 Medium 2026-10-22
CVE-2026-113260 Chrome 156 之前版本 Core 组件内存破坏漏洞 — Chrome - - 2026-10-20
CVE-2026-113344 Chrome 156 前 Performance 组件 Use-After-Free 漏洞 — Chrome - - 2026-10-20
CVE-2026-113380 Signal RingRTC 2.72.0 前队列饱和导致无法挂断 — RingRTC 9.3 Critical 2026-10-20
CVE-2026-100352 kin-openapi: YAML NaN/Inf Values Bypass Built-in Guards and Panic via OAS 3.1 Validation Path — kin-openapi 7.5 High 2026-10-15
CVE-2026-0317 PAN-OS: Denial of Service Vulnerability — Cloud NGFW 1.2 Low 2026-10-14
CVE-2026-0318 PAN-OS: Denial of Service (DoS) on Panorama — Cloud NGFW 4.6 Medium 2026-10-14
CVE-2026-0319 PAN-OS: Improper Input Handling Vulnerability — Cloud NGFW 4.9 Medium 2026-10-14
CVE-2026-0321 PAN-OS: Denial of Service (DoS) Vulnerabilities in Network Services — Cloud NGFW 6.6 Medium 2026-10-14

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