CWE-1310: Missing Ability to Patch ROM Code
Missing an ability to patch ROM code may leave a System or System-on-Chip (SoC) in a vulnerable state.
How it's found
Missing Ability to Patch ROM Code is typically found by tracing untrusted input from where it enters the system to the point where it is used without the check or neutralization this weakness describes, combining manual code review with dynamic testing.
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.
Vulnerable vs. safe
.clk_i ,.req_i ( rom_req ),.addr_i ( rom_addr ),.rdata_o ( rom_rdata_patch )
.clk_i ,.req_i ( rom_req ),.addr_i ( rom_addr ),.rdata_o ( rom_rdata_linux )bootrom i_bootrom_patch ();bootrom_linux i_bootrom_linux ();assign rom_rdata = (ariane_boot_sel_i) ? rom_rdata_linux : rom_rdata_linux;.......clk_i ,.req_i ( rom_req ),.addr_i ( rom_addr ),.rdata_o ( rom_rdata_patch )
.clk_i ,.req_i ( rom_req ),.addr_i ( rom_addr ),.rdata_o ( rom_rdata_linux )bootrom i_bootrom_patch ();bootrom_linux i_bootrom_linux ();assign rom_rdata = (ariane_boot_sel_i) ? rom_rdata_patch : rom_rdata_linux;......Consequences
- Varies by Context, Reduce Maintainability: When the system is unable to be patched, it can be left in a vulnerable state.
Mitigations
- Architecture and Design/Implementation: Secure patch support to allow ROM code to be patched on the next boot.
- Architecture and Design/Implementation: 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.
Where this fits in a TurboPentest engagement
TurboPentest's agentic pentest is powerful and covers a broad range of issues automatically. This particular class is best confirmed in a manual IntegSec engagement, where human pentesters apply deeper methodology and a larger context window than any automated pass.
Frequently asked questions
What is CWE-1310?
Missing an ability to patch ROM code may leave a System or System-on-Chip (SoC) in a vulnerable state.
How do you find Missing Ability to Patch ROM Code?
Missing Ability to Patch ROM Code is typically found by tracing untrusted input from where it enters the system to the point where it is used without the check or neutralization this weakness describes, combining manual code review with dynamic testing.
What is the impact of CWE-1310?
Varies by Context, Reduce Maintainability: When the system is unable to be patched, it can be left in a vulnerable state.
Does TurboPentest test for Missing Ability to Patch ROM Code?
TurboPentest's agentic pentest is powerful and covers a broad range of issues automatically. This particular class is best confirmed in a manual IntegSec engagement, where human pentesters apply deeper methodology and a larger context window than any automated pass.
Related CWEs
Find these issues before an attacker does
TurboPentest runs an agentic AI pentest against your target and reports findings with proof, from $99 per target.
Start a $99 pentest