名稱: Missing Ability to Patch ROM Code
Missing an ability to patch ROM code may leave a System or System-on-Chip (SoC) in a vulnerable state.
一般資訊
引入方式
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.
適用平台
程式語言
類別： Not Language-Specific (Undetermined)作業系統
類別： Not OS-Specific (Undetermined)架構
類別： Not Architecture-Specific (Undetermined)技術
類別： System on Chip (Undetermined)常見後果
| 範圍 | 影響 | 可能性 |
|---|---|---|
| Other | Varies by Context, Reduce Maintainability 注意：Because the code in ROM is immutable, the ROM does not have the ability to patch after the system gets shipped. Hence any security vulnerabilities discovered in the ROM code can never be fixed for the systems that are already in use. Thus the system can be left in a vulnerable state where an adversary can compromise the SoC.. | High |
潛在緩解措施
Phases : Architecture and Design // ImplementationSecure patch support to allow ROM code to be patched on the next boot.
Phases : 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.
漏洞對應備注
理由說明 : This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.備註 : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
相關攻擊模式
| CAPEC ID | 攻擊模式名稱 |
|---|---|
| CAPEC-682 | Exploitation of Firmware or ROM Code with Unpatchable Vulnerabilities
An adversary may exploit vulnerable code (i.e., firmware or ROM) that is unpatchable. Unpatchable devices exist due to manufacturers intentionally or inadvertently designing devices incapable of updating their software. Additionally, with updatable devices, the manufacturer may decide not to support the device and stop making updates to their software. |
參考資料
REF-1396
riscv_peripherals.sv line 534https://github.com/HACK-EVENT/hackatdac21/blob/75e5c0700b5a02e744f006fe8a09ff3c2ccdd32d/piton/design/chip/tile/ariane/openpiton/riscv_peripherals.sv#L534
REF-1397
Fix for riscv_peripherals.sv line 534https://github.com/HACK-EVENT/hackatdac21/blob/cwe_1310_riscv_peripheral/piton/design/chip/tile/ariane/openpiton/riscv_peripherals.sv#L534
提交
| 名稱 | 機構 | 日期 | 發布日期 | Version |
|---|---|---|---|---|
| Narasimha Kumar V Mangipudi | Intel Corporation | 4.3 |
修改記錄
| 名稱 | 機構 | 日期 | 備註 |
|---|---|---|---|
| CWE Content Team | MITRE | updated Maintenance_Notes | |
| CWE Content Team | MITRE | updated Demonstrative_Examples, Maintenance_Notes | |
| CWE Content Team | MITRE | updated Applicable_Platforms, Common_Consequences, Potential_Mitigations, Relationships | |
| CWE Content Team | MITRE | updated References, Related_Attack_Patterns | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Mapping_Notes | |
| CWE Content Team | MITRE | updated Demonstrative_Examples, References | |
| CWE Content Team | MITRE | updated Weakness_Ordinalities | |
| CWE Content Team | MITRE | updated Common_Consequences, Demonstrative_Examples, Description |
