CVE-2025-34502
Raw vector
CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2025-34502 is a high-severity Missing Immutable Root of Trust in Hardware (CWE-1326) vulnerability in Ioactive (inferred from references). Its CVSS base score is 7.0 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Pre-OS Boot (T1542); ranked at the 10th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SC-34 (Non-modifiable Executable Programs) and SC-51 (Hardware-based Protection) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-35894
Vulnerability Data
Deck Mate 2 lacks a verified secure-boot chain and runtime integrity validation for its controller and display modules. Without cryptographic boot verification, an attacker with physical access can modify or replace the bootloader, kernel, or filesystem and gain persistent code…
more
execution on reboot. This weakness allows long-term firmware tampering that survives power cycles. The vendor indicates that more recent firmware updates strengthen update-chain integrity and disable physical update ports to mitigate related attack avenues.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Requires hardware-enforced loading and execution of the operating environment from a protected source, directly establishing an immutable hardware root of trust.
Mandates hardware-based write-protect mechanisms that can implement and protect an immutable root of trust against tampering.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Assessing hardware authenticity/integrity before acquisition directly prevents purchase of devices lacking an immutable root of trust.
Replacing hardware that lacks required security capabilities (e.g., immutable root of trust) mitigates the weakness over the asset lifecycle.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure system architecture and engineering principles require hardware roots of trust to prevent bypass of secure boot.
Cryptographic controls can protect the root of trust but do not mandate its hardware immutability.
Change management can protect firmware updates but does not ensure an immutable hardware root of trust exists.
Configuration management can enforce secure boot settings but does not address the absence of an immutable hardware root.