CWEweakness

CWE-1243 Sensitive Non-Volatile Information Not Protected During Debug

Official page ↗
Abstraction
Base
Structure
Simple
Status
Incomplete
Languages
Not Language-Specific
CWE version
5.0

Description

Access to security-sensitive information stored in fuses is not limited during debug.

Extended description

Several security-sensitive values are programmed into fuses to be used during early-boot flows or later at runtime. Examples of these security-sensitive values include root keys, encryption keys, manufacturing-specific information, chip-manufacturer-specific information, and original-equipment-manufacturer (OEM) data. After the chip is powered on, these values are sensed from fuses and stored in temporary locations such as registers and local memories. These locations are typically access-control protected from untrusted agents capable of accessing them. Even to trusted agents, only read-access is provided.

Common consequences

• Confidentiality, Access Control: Modify Memory, Read Memory, Bypass Protection Mechanism — If these locations are not blocked during debug operations, it can allow a user to access this sensitive information.

Potential mitigations

• [Architecture and Design, Implementation] Disable access to security-sensitive information stored in fuses directly and also reflected from temporary storage locations when in debug mode.

Related

Attack pattern · CAPEC (2)

  • CAPEC-116 Excavation attack pattern
  • CAPEC-545 Pull Data from System Resources attack pattern

Child of · CWE (1)

  • CWE-1263 Improper Physical Access Control weakness

Referenced by CAPEC · weakness (2)

  • CAPEC-116 Excavation attack pattern
  • CAPEC-545 Pull Data from System Resources attack pattern