Back to CWE Database

CWE-1310

Missing Ability to Patch ROM Code

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

Potential Mitigations

Architecture and DesignImplementation

Secure patch support to allow ROM code to be patched on the next boot.

Effectiveness: Moderate

Architecture and DesignImplementation

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.

Effectiveness: Moderate

Common Consequences

Other
Varies by ContextReduce Maintainability

When the system is unable to be patched, it can be left in a vulnerable state.

Related Weaknesses