CWEweakness
CWE-1313 Hardware Allows Activation of Test or Debug Logic at Runtime
- Abstraction
- Base
- Structure
- Simple
- Status
- Draft
- Languages
- Not Language-Specific
- CWE version
- 5.0
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.
Common consequences
• 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 — 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 mitigations
• [Architecture and Design] 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.
• [Implementation] 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.
• [Integration] 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.
Observed examples
• 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
Attack pattern · CAPEC (1)
- CAPEC-121 Exploit Non-Production Interfaces attack pattern
Observed example · CVE (2)
- CVE-2021-33150 Hardware allows activation of test or debug logic at runtime for some Intel(R) Trace Hub instances which may allow an unauthenticated user… vulnerability
- CVE-2021-0146 Hardware allows activation of test or debug logic at runtime for some Intel(R) processors which may allow an unauthenticated user to… vulnerability
Child of · CWE (1)
- CWE-284 Improper Access Control weakness
Referenced by CAPEC · weakness (1)
- CAPEC-121 Exploit Non-Production Interfaces attack pattern
Referenced by CVE · weakness (2)
- CVE-2026-36027 An issue in Code27 Companion Hub SQ3A.220705.003.A1 allows a physically proximate attacker to execute arbitrary code via the USB debugging… vulnerability
- CVE-2025-2919 A vulnerability was found in Netis WF-2404 1.1.124EN. vulnerability