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.”
CVE References
More Stories
The Most Dangerous Vulnerabilities in Apache Tomcat and How to Protect Against Them
Apache Tomcat is an open-source web server and servlet container that is widely used in enterprise environments to run Java...
ZDI-CAN-18333: A Critical Zero-Day Vulnerability in Microsoft Windows
Zero-day vulnerabilities are a serious threat to cybersecurity, as they can be exploited by malicious actors to gain unauthorized access...
CWE-669 – Incorrect Resource Transfer Between Spheres
Description The product does not properly transfer a resource/behavior to another sphere, or improperly imports a resource/behavior from another sphere,...
CWE-67 – Improper Handling of Windows Device Names
Description The software constructs pathnames from user input, but it does not handle or incorrectly handles a pathname containing a...
CWE-670 – Always-Incorrect Control Flow Implementation
Description The code contains a control flow path that does not reflect the algorithm that the path is intended to...
CWE-671 – Lack of Administrator Control over Security
Description The product uses security features in a way that prevents the product's administrator from tailoring security settings to reflect...