CWE · MITRE source
CWE-1259Improper Restriction of Security Token Assignment
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.
Last updated: 04 July 2026 00:28 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: partial · 1 mapping(s) from 1 framework(s): CAPEC 1 (partial)
NIST 800-53 r5 controls that address this weakness (0)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
MITRE ATT&CK techniques this weakness enables
Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing). Drafted by Grok and spot-checked by Claude Opus 4.8.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2024-36533 | 7.0 | 9.8 | 0.0048 | 2024-07-24 |
CVE-2024-29371 | 5.5 | 7.5 | 0.0024 | 2025-12-17 |
CVE-2026-25700 UPD | 5.5 | 7.2 | 0.0045 | 2026-06-10 |
CVE-2022-23551 | 3.5 | 5.3 | 0.0071 | 2022-12-21 |
CVE-2022-23541 | 3.5 | 5.0 | 0.0075 | 2022-12-22 |
CVE-2024-36111 | 3.5 | 6.3 | 0.0839 | 2024-07-25 |
CVE-2024-45448 | 3.5 | 4.1 | 0.0010 | 2024-09-04 |
CVE-2025-27955 UPD | 3.5 | 6.5 | 0.0029 | 2025-06-02 |
CVE-2025-51306 UPD | 3.5 | 6.5 | 0.0035 | 2025-08-06 |
CVE-2025-50579 UPD | 3.5 | 5.3 | 0.0036 | 2025-08-19 |
CVE-2024-4598 | 3.5 | 6.5 | 0.0030 | 2025-09-23 |
CVE-2025-56676 | 3.5 | 5.4 | 0.0031 | 2025-09-30 |
CVE-2025-56207 | 3.5 | 6.5 | 0.0031 | 2025-09-30 |
CVE-2024-41948 | 1.5 | 3.0 | 0.0028 | 2024-08-01 |
CVE-2026-40264 | 1.5 | 2.7 | 0.0030 | 2026-04-21 |