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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%
Buy Us a Coffee

CWE-1310 — Vulnerability Class 1

1 vulnerabilities classified as CWE-1310. AI Chinese analysis included.

CWE-1310 represents a critical architectural weakness where a System-on-Chip lacks the capability to patch immutable Read-Only Memory code. Because ROM-based bootloaders often establish the Root-of-Trust, any discovered vulnerabilities remain permanently exploitable, allowing attackers to bypass security mechanisms or execute arbitrary code with persistent privileges. This immutable nature prevents standard software updates from mitigating flaws, effectively locking the device into a vulnerable state. To avoid this, developers must implement secure boot processes that verify code integrity before execution and design hardware architectures supporting secure, authenticated firmware updates for critical boot components. By ensuring that only verified, updatable code runs during the initial boot phase, organizations can maintain system integrity and prevent long-term exploitation of foundational hardware vulnerabilities.

MITRE CWE Description
Missing an ability to patch ROM code may leave a System or System-on-Chip (SoC) in a vulnerable state. A System or System-on-Chip (SoC) that implements a boot process utilizing security mechanisms such as Root-of-Trust (RoT) typically starts by executing code from a Read-only-Memory (ROM) component. The code in ROM is immutable, hence any security vulnerabilities discovered in the ROM code can never be fixed for the systems that are already in use. A common weakness is that the ROM does not have the ability to patch if security vulnerabilities are uncovered after the system gets shipped. This leaves the system in a vulnerable state where an adversary can compromise the SoC.
Common Consequences (1)
OtherVaries by Context, Reduce Maintainability
When the system is unable to be patched, it can be left in a vulnerable state.
Mitigations (2)
Architecture and Design, ImplementationSecure patch support to allow ROM code to be patched on the next boot.
Effectiveness: Moderate
Architecture and Design, ImplementationSupport patches that can be programmed in-field or during manufacturing through hardware fuses. This feature can be used for limited patching of devices after shipping, or for the next batch of silicon devices manufactured, without changing the full device ROM.
Effectiveness: Moderate
Examples (2)
A System-on-Chip (SOC) implements a Root-of-Trust (RoT) in ROM to boot secure code. However, at times this ROM code might have security vulnerabilities and need to be patched. Since ROM is immutable, it can be impossible to patch.
The example code is taken from the SoC peripheral wrapper inside the buggy OpenPiton SoC of HACK@DAC'21. The wrapper is used for connecting the communications between SoC peripherals, such as crypto-engines, direct memory access (DMA), reset controllers, JTAG, etc. The secure implementation of the SoC wrapper should allow users to boot from a ROM for Linux (i_bootrom_linux) or from a patchable ROM…
... bootrom i_bootrom_patch ( .clk_i                   , .req_i      ( rom_req   ), .addr_i     ( rom_addr  ), .rdata_o    ( rom_rdata_patch ) ); bootrom_linux i_bootrom_linux ( .clk_i                   , .req_i      ( rom_req   ), .addr_i     ( rom_addr  ), .rdata_o    ( rom_rdata_linux ) ); assign rom_rdata = (ariane_boot_sel_i) ? rom_rdata_linux : rom_rdata_linux; ...
Bad · Verilog
... bootrom i_bootrom_patch ( .clk_i                   , .req_i      ( rom_req   ), .addr_i     ( rom_addr  ), .rdata_o    ( rom_rdata_patch ) ); bootrom_linux i_bootrom_linux ( .clk_i                   , .req_i      ( rom_req   ), .addr_i     ( rom_addr  ), .rdata_o    ( rom_rdata_linux ) ); assign rom_rdata = (ariane_boot_sel_i) ? rom_rdata_patch : rom_rdata_linux; ...
Good · Verilog
CVE IDTitleCVSSSeverityPublished
CVE-2025-55338 Windows BitLocker Security Feature Bypass Vulnerability — Windows 10 Version 1507 6.1 Medium2025-10-14

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