Missing Ability to Patch ROM Code

Opis

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.

Skutki

• Other

  Varies by Context; Reduce Maintainability

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

Zapobieganie

• Architecture and Design, Implementation

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

  Skuteczność: Moderate

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

  Skuteczność: Moderate

Słabość nadrzędna

• CWE-1329 Reliance on Component That is Not Updateable

Kiedy powstaje

• Architecture and Design — This issue could be introduced during hardware architecture and design and can be identified later during Testing.
• Implementation — This issue could be introduced during implementation and can be identified later during Testing.
• Integration — This issue could be introduced during integration and can be identified later during Testing.
• Manufacturing — This issue could be introduced during manufacturing and can be identified later during Testing.

Dotyczy

Not Language-Specific, Not OS-Specific, Not Architecture-Specific, System on Chip

Źródła

1. riscv_peripherals.sv line 534 — 2021
2. Fix for riscv_peripherals.sv line 534 — 2021