Missing Ability to Patch ROM Code
CWE-1310
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.
We track 1 vulnerability of this type. 100% are rated high or critical, and the average CVSS score is 7.5.
How this weakness is prevented
- 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.
Latest Missing Ability to Patch ROM Code vulnerabilities
- 7.5 High severity
Red Hat Enterprise Linux 10: Incorrect Check of Function Return Value
A flaw was found in libssh. Incorrect AES-GCM finalization checks in builds using the OpenSSL backend can effectively remove integrity protection, allowing an in-path attacker to modify plaintext on the wire without detection.