Description
Missing an ability to patch ROM code may leave a System or System-on-Chip (SoC) in a vulnerable state.
Modes of Introduction:
– Architecture and Design
Related Weaknesses
Consequences
Other: Varies by Context, Reduce Maintainability
When the system is unable to be patched, it can be left in a vulnerable state.
Potential Mitigations
Phase: Architecture and Design, Implementation
Effectiveness: Moderate
Description:
Secure patch support to allow ROM code to be patched on the next boot.
Some parts of the hardware initialization or signature verification done to authenticate patches will always be “not patchable.”
Phase: Architecture and Design, Implementation
Effectiveness: Moderate
Description:
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.
Patches that use hardware fuses will have limitations in terms of size and the number of patches that can be supported. Note that some parts of the hardware initialization or signature verification done to authenticate patches will always be “not patchable.”