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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-1245 — Vulnerability Class 2

2 vulnerabilities classified as CWE-1245. AI Chinese analysis included.

CWE-1245 represents a critical design flaw in hardware logic where finite state machines are improperly implemented, leading to undefined operational states. This weakness typically allows attackers to manipulate the system’s control flow, forcing it into unintended configurations that can result in denial of service or unauthorized privilege escalation. By exploiting these logical gaps, adversaries bypass security mechanisms that rely on accurate state tracking for sensitive data operations. To mitigate this risk, developers must rigorously verify state transition logic during the design phase, ensuring all possible inputs lead to defined, secure states. Comprehensive testing, including formal verification methods and fuzzing, helps identify unreachable or ambiguous states. Additionally, implementing robust error-handling routines and redundant state checks ensures that the hardware logic remains resilient against malicious inputs, thereby maintaining system integrity and preventing exploitation of FSM vulnerabilities.

MITRE CWE Description
Faulty finite state machines (FSMs) in the hardware logic allow an attacker to put the system in an undefined state, to cause a denial of service (DoS) or gain privileges on the victim's system. The functionality and security of the system heavily depend on the implementation of FSMs. FSMs can be used to indicate the current security state of the system. Lots of secure data operations and data transfers rely on the state reported by the FSM.
Common Consequences (1)
Availability, Access ControlUnexpected State, DoS: Crash, Exit, or Restart, DoS: Instability, Gain Privileges or Assume Identity
Faulty FSM designs that do not account for all states, either through undefined states (left as don't cares) or through incorrect implementation, might lead an attacker to drive the system into an unstable state from which the system cannot recover without a reset, thus causing a DoS. Depending on w…
Mitigations (1)
Architecture and Design, ImplementationDefine all possible states and handle all unused states through default statements. Ensure that system defaults to a secure state.
Effectiveness: High
Examples (1)
The Finite State Machine (FSM) shown in the "bad" code snippet below assigns the output ("out") based on the value of state, which is determined based on the user provided input ("user_input").
module fsm_1(out, user_input, clk, rst_n); input [2:0] user_input; input clk, rst_n; output reg [2:0] out; reg [1:0] state; always @ (posedge clk or negedge rst_n ) begin if (!rst_n) state = 3'h0; else case (user_input) 3'h0: 3'h1: 3'h2: 3'h3: state = 2'h3; 3'h4: state = 2'h2; 3'h5: state = 2'h1; endcase end out <= {1'h1, state}; endmodule
Bad · Verilog
case (user_input) 3'h0: 3'h1: 3'h2: 3'h3: state = 2'h3; 3'h4: state = 2'h2; 3'h5: state = 2'h1; default: state = 2'h0; endcase
Good · Verilog
CVE IDTitleCVSSSeverityPublished
CVE-2025-48508 AMD Graphics Driver 安全漏洞 — AMD Radeon™ PRO V710 6.0 Medium2026-02-11
CVE-2024-58311 Dormakaba Saflok System 6000 Key Generation Cryptographic Weakness — Dormakaba Saflok System 6000 9.8 Critical2025-12-12

Vulnerabilities classified as CWE-1245 represent 2 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.