Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-1313 — Vulnerability Class 1

1 vulnerabilities classified as CWE-1313. AI Chinese analysis included.

CWE-1313 represents a critical hardware design flaw where test or debug logic remains accessible and activatable during normal runtime operations. This weakness allows adversaries to bypass standard security controls by altering the internal state of the hardware, potentially leading to unauthorized data leakage or complete system compromise. Attackers typically exploit this vulnerability by triggering debug interfaces through physical access, side-channel attacks, or malicious firmware updates that re-enable dormant diagnostic ports. To mitigate this risk, developers must implement robust hardware security measures, such as permanently disabling debug ports after manufacturing or utilizing secure boot mechanisms that verify firmware integrity. Additionally, employing hardware-enforced access controls and regular security audits ensures that diagnostic features remain isolated from production environments, thereby preventing unauthorized runtime activation and preserving the confidentiality and integrity of sensitive system data.

MITRE CWE 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.
Common Consequences (1)
Confidentiality, Integrity, AvailabilityModify 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 (3)
Architecture and DesignInsert 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 feat…
ImplementationInsert 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 feat…
IntegrationInsert 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 feat…
CVE IDTitleCVSSSeverityPublished
CVE-2025-2919 Netis WF-2404 UART hardware allows activation of test or debug logic at runtime — WF-2404 6.8 Medium2025-03-28

Vulnerabilities classified as CWE-1313 represent 1 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.