Description
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.
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.
Potential Impact
Confidentiality, Integrity, Availability
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
Mitigations & Prevention
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.
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.
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.
Real-World CVE Examples
| CVE ID | Description |
|---|---|
| CVE-2021-33150 | Hardware processor allows activation of test or debug logic at runtime. |
| CVE-2021-0146 | Processor allows the activation of test or debug logic at runtime, allowing escalation of privileges |
Related Weaknesses
Frequently Asked Questions
What is CWE-1313?
CWE-1313 (Hardware Allows Activation of Test or Debug Logic at Runtime) is a software weakness identified by MITRE's Common Weakness Enumeration. It is classified as a Base-level weakness. 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 a...
How can CWE-1313 be exploited?
Attackers can exploit CWE-1313 (Hardware Allows Activation of Test or Debug Logic at Runtime) to 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. This weakness is typically introduced during the Architecture and Design, Implementation, Integration phase of software development.
How do I prevent CWE-1313?
Key mitigations include: 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 canno
What is the severity of CWE-1313?
CWE-1313 is classified as a Base-level weakness (Medium abstraction). It has been observed in 2 real-world CVEs.