CWE-1310 詳細

CWE-1310

Missing Ability to Patch ROM Code
2020-12-10
00h00 +00:00
Draft
2026-10-28
00h00 +00:00
特定のCWEの通知
特定のCWEの変更情報をいち早くお届けします。
通知を管理する

名前: 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)

一般的な結果

スコープ 影響 可能性
OtherVaries 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 // Implementation
Secure 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 534
https://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 534
https://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 2020-04-25 +00:00 2020-12-10 +00:00 4.3

変更履歴

名前 組織 日付 コメント
CWE Content Team MITRE 2021-03-15 +00:00 updated Maintenance_Notes
CWE Content Team MITRE 2021-07-20 +00:00 updated Demonstrative_Examples, Maintenance_Notes
CWE Content Team MITRE 2022-04-28 +00:00 updated Applicable_Platforms, Common_Consequences, Potential_Mitigations, Relationships
CWE Content Team MITRE 2022-10-13 +00:00 updated References, Related_Attack_Patterns
CWE Content Team MITRE 2023-04-27 +00:00 updated Relationships
CWE Content Team MITRE 2023-06-29 +00:00 updated Mapping_Notes
CWE Content Team MITRE 2024-02-29 +00:00 updated Demonstrative_Examples, References
CWE Content Team MITRE 2025-12-11 +00:00 updated Weakness_Ordinalities
CWE Content Team MITRE 2026-10-28 +00:00 updated Common_Consequences, Demonstrative_Examples, Description