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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%
Buy Us a Coffee

CWE-1259 — Vulnerability Class 5

5 vulnerabilities classified as CWE-1259. AI Chinese analysis included.

CWE-1259 represents a critical architectural flaw in System-On-A-Chip designs where security tokens, used to authenticate and authorize specific actions, are inadequately protected. This weakness allows attackers to manipulate or forge these tokens, effectively bypassing access controls to execute unauthorized operations or impersonate legitimate agents within the hardware environment. Exploitation typically involves intercepting, modifying, or replaying token data to trick the SoC into granting elevated privileges or accessing restricted resources. To mitigate this risk, developers must implement robust cryptographic safeguards, such as digital signatures and encryption, to ensure token integrity and authenticity. Additionally, employing secure key management practices and regular security audits helps prevent token exposure, ensuring that only valid, unaltered tokens are accepted for transaction processing within the embedded system.

MITRE CWE Description
The System-On-A-Chip (SoC) implements a Security Token mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. However, the Security Tokens are improperly protected. Systems-On-A-Chip (Integrated circuits and hardware engines) implement Security Tokens to differentiate and identify which actions originated from which agent. These actions may be one of the directives: 'read', 'write', 'program', 'reset', 'fetch', 'compute', etc. Security Tokens are assigned to every agent in the System that is capable of generating an action or receiving an action from another agent. Multiple Security Tokens may be assigned to an agent and may be unique based on the agent's trust level or allowed privileges. Since the Security Tokens are integral for the maintenance of security in an SoC, they need to be protected properly. A common weakness afflicting Security Tokens is improperly restricting the assignment to trusted components.
Common Consequences (1)
Confidentiality, Integrity, Availability, Access ControlModify Files or Directories, Execute Unauthorized Code or Commands, Bypass Protection Mechanism, Gain Privileges or Assume Identity, Modify Memory, Modify Memory, DoS: Crash, Exit, or Restart
An improperly protected Security Token may be able to be programmed by a malicious agent (i.e., the Security Token is mutable) to spoof the action as if it originated from a trusted agent.
Mitigations (1)
Architecture and Design, ImplementationSecurity Token assignment review checks for design inconsistency and common weaknesses. Security-Token definition and programming flow is tested in both pre-silicon and post-silicon testing.
Examples (1)
For example, consider a system with a register for storing an AES key for encryption and decryption. The key is of 128 bits implemented as a set of four 32-bit registers. The key register assets have an associated control register, AES_KEY_ACCESS_POLICY, which provides the necessary access controls. This access-policy register defines which agents may engage in a transaction, and the type of trans…
The Aux-controller could program its Security Token to "1" from "2".
Bad · Other
The SoC needs to protect the Security Tokens. None of the agents in the SoC should have the ability to change the Security Token.
Good · Other
CVE IDTitleCVSSSeverityPublished
CVE-2026-40264 OpenBao's Token Store Allows Cross-Namespace Renewal, Revocation — openbao 8.1AIHighAI2026-04-21
CVE-2024-45448 Huawei HarmonyOS 安全漏洞 — HarmonyOS 4.1 Medium2024-09-04
CVE-2024-41948 biscuit-java vulnerable to public key confusion in third party block — biscuit-java 3.0 Low2024-08-01
CVE-2024-36111 KubePi's JWT token validation has a defect — KubePi 6.3 Medium2024-07-25
CVE-2022-23551 AAD Pod Identity obtaining token with backslash — aad-pod-identity 5.3 Medium2022-12-21

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