CWE-1313

Hardware Allows Activation of Test or Debug Logic at Runtime
AI Translation Available

During runtime, the hardware allows for test or debug logic (feature) to be activated, which allows for changing the state of the hardware. This feature can alter the intended behavior of the system and allow for alteration and leakage of sensitive data by an adversary.

Status
draft
Abstraction
base

An adversary can take advantage of test or debug logic that is made accessible through the hardware during normal operation to modify the intended behavior of the system. For example, an accessible Test/debug mode may allow read/write access to any system data. Using error injection (a common test/debug feature) during a transmit/receive operation on a bus, data may be modified to produce an unintended message. Similarly, confidentiality could be compromised by such features allowing access to secrets.

Common Consequences

confidentiality integrity availability
Impacts
modify memory read memory dos: crash, exit, or restart dos: instability dos: resource consumption (cpu) dos: resource consumption (memory) dos: resource consumption (other) execute unauthorized code or commands gain privileges or assume identity bypass protection mechanism alter execution logic quality degradation unexpected state reduce performance reduce reliability

Potential Mitigations

Phases:
architecture and design implementation integration
Descriptions:
• Insert restrictions on when the hardware's test or debug features can be activated. For example, during normal operating modes, the hardware's privileged modes that allow access to such features cannot be activated. Configuring the hardware to only enter a test or debug mode within a window of opportunity such as during boot or configuration stage. The result is disablement of such test/debug features and associated modes during normal runtime operations.