CWE · MITRE source
CWE-1270Generation of Incorrect Security Tokens
The product implements a Security Token mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. However, the Security Tokens generated in the system are incorrect.
Systems-On-a-Chip (SoC) (Integrated circuits and hardware engines) implement Security Tokens to differentiate and identify actions originated from various agents. These actions could be "read", "write", "program", "reset", "fetch", "compute", etc. Security Tokens are generated and assigned to every agent on the SoC that is either capable of generating an action or receiving an action from another agent. Every agent could be assigned a unique, Security Token based on its trust level or privileges.
Last updated: 15 October 2026 14:21 UTC
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
NIST 800-53 r5 controls PROPOSED for this weakness (0)AI-assisted
These are model PROPOSALS, not graded mappings. They come
from controls_to_cwe_proposals, which carries no grade field at
all; across the CWE pages 1,540 of 1,722 such associations (89%) have never
been graded by anything. The heading said “address” until
2026-09-29, which asserted a relationship the data does not carry.
Graded cross-walks are on the framework map, not here.
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2022-31122 UPD | 7.4 | 9.8 | 0.0072 | 2022-10-18 |
CVE-2023-2882 UPD | 7.4 | 9.8 | 0.0064 | 2023-05-25 |
CVE-2026-49499 UPD | 6.5 | 8.8 | 0.0042 | 2026-07-22 |
CVE-2026-54593 | 6.2 | 8.1 | 0.0068 | 2026-07-28 |
CVE-2025-59698 UPD | 5.1 | 6.8 | 0.0033 | 2025-12-02 |
CVE-2023-22644 UPD | 4.4 | 5.5 | 0.0046 | 2023-09-20 |
CVE-2026-19636 | 4.1 | 5.3 | 0.0026 | 2026-08-14 |
CVE-2023-30524 UPD | 3.7 | 4.3 | 0.0043 | 2023-04-12 |
CVE-2026-15831 | 3.6 | 4.3 | 0.0030 | 2026-07-29 |