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-2024-39545 Junos OS: SRX Series, MX Series with SPC3 and NFX350: When VPN tunnels parameters are not configured in specific way the iked process will crash — Junos OS 7.5 High2024-07-11
CVE-2024-39540 Junos OS: SRX Series, and MX Series with SPC3: Specific valid TCP traffic can cause a pfe crash — Junos OS 7.5 High2024-07-11
CVE-2024-39535 Junos OS Evolved: ACX 7000 Series: When specific traffic is received in a VPLS scenario evo-pfemand crashes — Junos OS Evolved 6.5 Medium2024-07-11
CVE-2024-39530 Junos OS: Attempting to access specific sensors on platforms not supporting these will lead to a chassisd crash — Junos OS 7.5 High2024-07-11
CVE-2024-39519 Junos OS Evolved: ACX 7000 Series: Multicast traffic is looped in a multihoming EVPN MPLS scenario — Junos OS Evolved 6.5 Medium2024-07-11
CVE-2024-37151 Suricata defrag: IP ID reuse can lead to policy bypass — suricata 5.3 Medium2024-07-11
CVE-2024-39517 Junos OS and Junos OS Evolved: Upon processing specific L2 traffic, rpd can hang in devices with EVPN/VXLAN configured — Junos OS 6.5 Medium2024-07-10
CVE-2024-39561 Junos OS: SRX4600, SRX5000 Series: TCP packets with SYN/FIN or SYN/RST are transferred after enabling no-syn-check with Express Path — Junos OS 5.8 Medium2024-07-10
CVE-2024-39559 Junos OS Evolved: Receipt of a specific TCP packet may result in a system crash (vmcore) on dual RE systems with NSR enabled — Junos OS Evolved 5.9 Medium2024-07-10
CVE-2024-39869 Siemens SINEMA Remote Connect 代码问题漏洞 — SINEMA Remote Connect Server 6.5 Medium2024-07-09
CVE-2024-21586 Junos OS: SRX Series and NFX Series: Specific valid traffic leads to a PFE crash — Junos OS 7.5 High2024-07-01
CVE-2024-34694 LNbits improperly handles potential network and payment failures when using Eclair backend — lnbits 8.1 High2024-06-14
CVE-2024-5469 Uncontrolled Resource Consumption in GitLab — GitLab 3.1 Low2024-06-14
CVE-2024-36128 Directus is soft-locked by providing a string value to random string util — directus 7.5 High2024-06-03
CVE-2023-52710 Huawei PC Manager 安全漏洞 — CurieM-WFG9B 7.8 High2024-05-28
CVE-2024-34360 Previous ATX is not checked to be the newest valid ATX by Smesher when validating incoming ATX — go-spacemesh 8.2 High2024-05-10
CVE-2024-32867 Suricata's defrag contains various issues leading to policy bypass — suricata 5.3 Medium2024-05-07
CVE-2024-4182 Mattermost 安全漏洞 — Mattermost 4.3 Medium2024-04-26
CVE-2024-30402 Junos OS and Junos OS Evolved: The l2ald crashes on receiving telemetry messages from a specific subscription — Junos OS 5.9 Medium2024-04-12
CVE-2024-30397 Junos OS: An invalid certificate causes a Denial of Service in the Internet Key Exchange (IKE) process — Junos OS 7.5 High2024-04-12
CVE-2024-30384 Junos OS: EX4300 Series: If a specific CLI command is issued PFE crashes will occur — Junos OS 5.5 Medium2024-04-12
CVE-2024-30409 Junos OS and Junos OS Evolved: Higher CPU consumption on routing engine leads to Denial of Service (DoS). — Junos OS 5.3 Medium2024-04-12
CVE-2024-23650 BuildKit possible panic when incorrect parameters sent from frontend — buildkit 5.3 Medium2024-01-31
CVE-2024-24567 raw_call `value=` kwargs not disabled for static and delegate calls — vyper 4.8 Medium2024-01-30
CVE-2024-0675 Improper checking for unusual or exceptional conditions vulnerability in Lamassu Bitcoin ATM Douro machines — Bitcoin ATM Douro machines 6.3 Medium2024-01-30
CVE-2024-22422 Unauthenticated Denial of Service (DOS) attack in AnythingLLM — anything-llm 7.5 High2024-01-19
CVE-2024-21614 Junos OS and Junos OS Evolved: A specific query via DREND causes rpd crash — Junos OS 7.5 High2024-01-12
CVE-2024-21603 Junos OS: MX Series: Gathering statistics in a scaled SCU/DCU configuration will lead to a device crash — Junos OS 6.5 Medium2024-01-12
CVE-2023-32726 Possible buffer overread from reading DNS responses — Zabbix 3.9 Low2023-12-18
CVE-2023-48431 Siemens SINEC INS 代码问题漏洞 — SINEC INS 6.8 Medium2023-12-12

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