Nama: Sensitive Information Uncleared Before Debug/Power State Transition

The product performs a power or debug state transition, but it does not clear sensitive information that should no longer be accessible due to changes to information access restrictions.

Informasi Umum

Detail Latar Belakang

Mode Pengenalan

Architecture and Design

Platform yang Berlaku

Bahasa

Nama: VHDL (Undetermined)
Nama: Verilog (Undetermined)
Kelas: Hardware Description Language (Undetermined)

Sistem Operasi

Kelas: Not OS-Specific (Undetermined)

Arsitektur

Kelas: Not Architecture-Specific (Undetermined)

Teknologi

Kelas: Not Technology-Specific (Undetermined)

Konsekuensi Umum

Cakupan	Dampak	Kemungkinan
Confidentiality Integrity Availability Access Control Accountability Authentication Authorization Non-Repudiation	Read Memory, Read Application Data Catatan: If there is information available in the previous state which should not be available in the next state and is not properly removed before the transition into the next state, sensitive information may leak from the system. The sensitive information may be used to unlock additional capabilities of the device and take advantage of hidden functionalities which could be used to compromise device security.	High

Contoh yang Diamati

Referensi	Deskripsi
CVE-2020-12926	Product software does not set a flag as per TPM specifications, thereby preventing a failed authorization attempt from being recorded after a loss of power.

Mitigasi yang Memungkinkan

Phases : Architecture and Design // Implementation
During state transitions, information not needed in the next state should be removed before the transition to the next state.

Metode Deteksi

Manual Analysis

Write a known pattern into each sensitive location. Enter the power/debug state in question. Read data back from the sensitive locations. If the reads are successful, and the data is the same as the pattern that was originally written, the test fails and the device needs to be fixed. Note that this test can likely be automated.
Efektivitas : High

Catatan Pemetaan Kerentanan

Justifikasi : 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.
Komentar : 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.

Pola Serangan Terkait

CAPEC ID	Nama Pola Serangan
CAPEC-150	Collect Data from Common Resource Locations An adversary exploits well-known locations for resources for the purposes of undermining the security of the target. In many, if not most systems, files and resources are organized in a default tree structure. This can be useful for adversaries because they often know where to look for resources or files that are necessary for attacks. Even when the precise location of a targeted resource may not be known, naming conventions may indicate a small area of the target machine's file tree where the resources are typically located. For example, configuration files are normally stored in the /etc director on Unix systems. Adversaries can take advantage of this to commit other types of attacks.
CAPEC-37	Retrieve Embedded Sensitive Data An attacker examines a target system to find sensitive data that has been embedded within it. This information can reveal confidential contents, such as account numbers or individual keys/credentials that can be used as an intermediate step in a larger attack.
CAPEC-545	Pull Data from System Resources An adversary who is authorized or has the ability to search known system resources, does so with the intention of gathering useful information. System resources include files, memory, and other aspects of the target system. In this pattern of attack, the adversary does not necessarily know what they are going to find when they start pulling data. This is different than CAPEC-150 where the adversary knows what they are looking for due to the common location.
CAPEC-546	Incomplete Data Deletion in a Multi-Tenant Environment An adversary obtains unauthorized information due to insecure or incomplete data deletion in a multi-tenant environment. If a cloud provider fails to completely delete storage and data from former cloud tenants' systems/resources, once these resources are allocated to new, potentially malicious tenants, the latter can probe the provided resources for sensitive information still there.

Referensi

REF-1220

Understanding the Security of ARM Debugging Features
Zhenyu Ning, Fengwei Zhang.
https://www.computer.org/csdl/proceedings-article/sp/2019/666000a602/1dlwieBPZ2o

Pengajuan

Nama	Organisasi	Tanggal	Tanggal rilis	Version
Parbati Kumar Manna, Hareesh Khattri, Arun Kanuparthi	Intel Corporation	2020-05-31 +00:00	2020-02-24 +00:00	4.1

Modifikasi

Nama	Organisasi	Tanggal	Komentar
CWE Content Team	MITRE	2020-08-20 +00:00	updated Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Description, Name, Potential_Mitigations, Related_Attack_Patterns, Relationships
CWE Content Team	MITRE	2021-03-15 +00:00	updated Functional_Areas
CWE Content Team	MITRE	2021-10-28 +00:00	updated Common_Consequences, Demonstrative_Examples, Description, Detection_Factors, Observed_Examples, Potential_Mitigations, References, Relationships, Weakness_Ordinalities
CWE Content Team	MITRE	2022-10-13 +00:00	updated Applicable_Platforms
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	2025-04-03 +00:00	updated Demonstrative_Examples
CWE Content Team	MITRE	2025-09-09 +00:00	updated References, Relationships
CWE Content Team	MITRE	2026-10-28 +00:00	updated Background_Details, Common_Consequences, Description, Relationships

Detail CWE-1272

CWE-1272