CWEweakness

CWE-1272 Sensitive Information Uncleared Before Debug/Power State Transition

Official page ↗
Abstraction
Base
Structure
Simple
Status
Stable
Languages
Hardware Description Language, VHDL, Verilog
CWE version
5.0

Description

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.

Common consequences

• Confidentiality, Integrity, Availability, Access Control, Accountability, Authentication, Authorization, Non-Repudiation: Read Memory, Read Application Data — 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.

Potential mitigations

• [Architecture and Design, Implementation] During state transitions, information not needed in the next state should be removed before the transition to the next state.

Detection methods

• 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.

Observed examples

• 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.

Related

Attack pattern · CAPEC (4)

  • CAPEC-150 Collect Data from Common Resource Locations attack pattern
  • CAPEC-37 Retrieve Embedded Sensitive Data attack pattern
  • CAPEC-545 Pull Data from System Resources attack pattern
  • CAPEC-546 Incomplete Data Deletion in a Multi-Tenant Environment attack pattern

Observed example · CVE (1)

  • CVE-2020-12926 The Trusted Platform Modules (TPM) reference software may not properly track the number of times a failed shutdown happens. vulnerability

Can also be · CWE (1)

  • CWE-1239 Improper Zeroization of Hardware Register weakness

Can precede · CWE (1)

  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor weakness

Child of · CWE (1)

  • CWE-226 Sensitive Information in Resource Not Removed Before Reuse weakness

Referenced by CAPEC · weakness (4)

  • CAPEC-150 Collect Data from Common Resource Locations attack pattern
  • CAPEC-37 Retrieve Embedded Sensitive Data attack pattern
  • CAPEC-545 Pull Data from System Resources attack pattern
  • CAPEC-546 Incomplete Data Deletion in a Multi-Tenant Environment attack pattern

Referenced by CVE · weakness (2)

  • CVE-2023-41967 Sensitive information uncleared after debug/power state transition in the Controller 6000 could be abused by an attacker with knowledge of… vulnerability
  • CVE-2020-22656 In Ruckus R310 10.5.1.0.199, Ruckus R500 10.5.1.0.199, Ruckus R600 10.5.1.0.199, Ruckus T300 10.5.1.0.199, Ruckus T301n 10.5.1.0.199,… vulnerability

Referenced by CWE · child of (2)

  • CWE-1239 Improper Zeroization of Hardware Register weakness
  • CWE-1258 Exposure of Sensitive System Information Due to Uncleared Debug Information weakness

Referenced by CWE · has member (1)

  • CWE-1343 Weaknesses in the 2021 CWE Most Important Hardware Weaknesses List view