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.
Common consequences1
- OtherVaries by ContextReduce Maintainability
When the system is unable to be patched, it can be left in a vulnerable state.
Potential mitigations2
- Architecture and DesignImplementationModerate
Secure patch support to allow ROM code to be patched on the next boot.
- Architecture and DesignImplementationModerate
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.
Relationships1
- ChildOfCWE-1329
CVEs referencing this CWE2
| CVE | Description | Severity | EPSS | Flags | Modified |
|---|---|---|---|---|---|
| CVE-2025-55338 | Missing Ability to Patch ROM Code in Windows BitLocker allows an unauthorized attacker to bypass a security feature with a physical attack. | MEDIUM4.6 | 2.89%p85 | 2026-02-22 | |
| CVE-2016-1000344 | In the Bouncy Castle JCE Provider version 1.55 and earlier the DHIES implementation allowed the use of ECB mode. This mode is regarded as unsafe and support for it has been removed from the provider. | HIGH7.4 | 2.19%p80 | 2025-09-12 |