CWE-1310: Missing Ability to Patch ROM Code

Extended Description

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.

Code Examples & CVEs

Demonstrative Examples

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 (i_bootrom_patch) if the Linux bootrom has security or functional issues.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 (i_bootrom_patch) if the Linux bootrom has security or functional issues.

The above implementation causes the ROM data to be hardcoded for the linux system (rom_rdata_linux) regardless of the value of ariane_boot_sel_i. Therefore, the data (rom_rdata_patch) from the patchable ROM code is never used [REF-1396]. This weakness disables the ROM's ability to be patched. If attackers uncover security vulnerabilities in the ROM, the users must replace the entire device. Otherwise, the weakness exposes the system to a vulnerable state forever. A fix to this issue is to enable rom_rdata to be selected from the patchable rom (rom_rdata_patch) [REF-1397].

BadVerilog

... 						 						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; 					...

GoodVerilog

... 						 						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; 					...

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-1310 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-1310, Missing Ability to Patch ROM Code, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Address Missing Ability to Patch ROM Code during Architecture and Design

MITRE associates mitigation with Architecture and Design, and Implementation; recorded impacts include Varies by Context, and Reduce Maintainability; the entry maps to CAPEC-682. Use these source-defined anchors to turn CWE-1310 into implementation, review, and verification checks for the affected component.

CWE-1310: Missing Ability to Patch ROM Code — MITRE CWE

Triage CWE-1310 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-1310, Missing Ability to Patch ROM Code, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-1310

Apply MITRE's full root-cause mapping guidance when using CWE-1310, Missing Ability to Patch ROM Code. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-1310 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-1310, Missing Ability to Patch ROM Code. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-1310: Missing Ability to Patch ROM Code?+

CWE-1310: Missing Ability to Patch ROM Code is a Common Weakness Enumeration (CWE) entry maintained by MITRE. 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.

What are the security consequences of Missing Ability to Patch ROM Code?+

If exploited, CWE-1310 (Missing Ability to Patch ROM Code) it can compromise Other, leading to outcomes such as Varies by Context and Reduce Maintainability.

How do you prevent or mitigate Missing Ability to Patch ROM Code?+

Recommended mitigations for CWE-1310 include: Secure patch support to allow ROM code to be patched on the next boot. Support 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.

Which programming languages are affected by Missing Ability to Patch ROM Code?+

CWE-1310 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-1310 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

CWE-1310: Missing Ability to Patch ROM Code

Extended Description

Technical Details

Applicable To

Security Consequences

Scope

Impact

Likelihood

Mitigation Strategies

Phase

Description

Effectiveness