Tên: Missing Immutable Root of Trust in Hardware

A missing immutable root of trust in the hardware results in the ability to bypass secure boot or execute untrusted or adversarial boot code.

Thông tin chung

Chi tiết nền tảng

Các cách xuất hiện

Architecture and Design
Implementation : Such issues could be introduced during policy definition, hardware architecture, design, manufacturing, and/or provisioning. They can be identified later during testing or system configuration phases.

Nền tảng áp dụng

Ngôn ngữ

Lớp: Not Language-Specific (Undetermined)

Hệ điều hành

Lớp: Not OS-Specific (Undetermined)

Kiến trúc

Lớp: Not Architecture-Specific (Undetermined)

Công nghệ

Tên: Security Hardware (Undetermined)
Lớp: Not Technology-Specific (Undetermined)

Hậu quả phổ biến

Phạm vi	Tác động	Khả năng xảy ra
Authentication Authorization	Gain Privileges or Assume Identity, Execute Unauthorized Code or Commands, Modify Memory	High

Các biện pháp giảm thiểu tiềm năng

Phases : Architecture and Design
When architecting the system, the RoT should be designated for storage in a memory that does not allow further programming/writes. Note that, for components like ROM, secure patching/update features should be supported to allow authenticated and authorized updates in the field.
Phases : Implementation
During implementation and test, the RoT memory location should be demonstrated to not allow further programming/writes.

Phương pháp phát hiện

Automated Dynamic Analysis

Automated testing can verify that RoT components are immutable.
Hiệu quả : High

Architecture or Design Review

Root of trust elements and memory should be part of architecture and design reviews.
Hiệu quả : High

Ghi chú ánh xạ lỗ hổng

Lý do : 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.
Bình luận : 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.

Mẫu tấn công liên quan

ID CAPEC	Tên mẫu tấn công
CAPEC-679	Exploitation of Improperly Configured or Implemented Memory Protections
CAPEC-68	Subvert Code-signing Facilities Many languages use code signing facilities to vouch for code's identity and to thus tie code to its assigned privileges within an environment. Subverting this mechanism can be instrumental in an attacker escalating privilege. Any means of subverting the way that a virtual machine enforces code signing classifies for this style of attack.

Tài liệu tham khảo

Gửi

Tên	Tổ chức	Ngày	Ngày phát hành	Version
Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna	Intel Corporation	2020-04-25 +00:00	2020-12-10 +00:00	4.3

Sửa đổi

Tên	Tổ chức	Ngày	Bình luận
CWE Content Team	MITRE	2021-10-28 +00:00	updated Demonstrative_Examples
CWE Content Team	MITRE	2022-04-28 +00:00	updated Applicable_Platforms, Related_Attack_Patterns
CWE Content Team	MITRE	2022-06-28 +00:00	updated Applicable_Platforms, Modes_of_Introduction
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	2023-10-26 +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 Background_Details, Common_Consequences, Demonstrative_Examples, Description, Potential_Mitigations

Chi tiết CWE-1326

CWE-1326