CWE-1270: Generation 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.
Last updated
Overview
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.
Real-world CVEs
5 recorded CVEs are caused by CWE-1270 (Generation of Incorrect Security Tokens). The highest-severity and most recent are shown first. 0 new CWE-1270 CVEs have been recorded so far in 2026 (1 in 2025).
- CVE-2023-2882
Privilege Escalation in CBOT's Chatbot
Critical · CVSS 9.8 · EPSS 47th2023-05-25 - CVE-2023-32188Critical · CVSS 9.4 · EPSS 37th2024-10-16
- CVE-2023-22644Critical · CVSS 9.4 · EPSS 36th2023-09-20
- CVE-2025-59698Medium · CVSS 6.8 · EPSS 18th2025-12-02
- CVE-2023-30524Medium · CVSS 4.3 · EPSS 35th2023-04-12
Common consequences
What can happen when CWE-1270 is exploited.
Modify Files or Directories, Execute Unauthorized Code or Commands, Bypass Protection Mechanism, Gain Privileges or Assume Identity, Read Memory, Modify Memory, DoS: Crash, Exit, or Restart
Affects: Confidentiality, Integrity, Availability, Access Control
Incorrectly generated Security Tokens could result in the same token used for multiple agents or multiple tokens being used for the same agent. This condition could result in a Denial-of-Service (DoS) or the execution of an action that in turn could result in privilege escalation or unintended access.
How it happens
When it is introduced
Typically introduced during these phases of the software lifecycle.
How to prevent it
Practical mitigations for CWE-1270, grouped by where in the lifecycle they apply.
- Generation of Security Tokens should be reviewed for design inconsistency and common weaknesses.
- Security-Token definition and programming flow should be tested in pre-silicon and post-silicon testing.
Code examples
Illustrative examples from MITRE showing how the weakness appears in code.
Consider a system with a register for storing an AES key for encryption or decryption. The key is 128 bits long implemented as a set of four 32-bit registers. The key registers are assets, and register, AES_KEY_ACCESS_POLICY, is defined to provide necessary access controls. The access-policy register defines which agents, using a Security Token, may access the AES-key registers. Each bit in this 32-bit register is used to define a Security Token. There could be a maximum of 32 Security Tokens that are allowed access to the AES-key registers. When set (bit = "1") bit number allows action from an agent whose identity matches that bit number. If Clear (bit = "0") the action is disallowed for the corresponding agent.
Attack patterns
CAPEC attack patterns that exploit this weakness.
Frequently asked questions
Common questions about CWE-1270.
- What is CWE-1270?
- 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.
- What CVEs are caused by CWE-1270?
- 5 recorded CVEs are attributed to CWE-1270, including CVE-2023-2882, CVE-2023-32188, CVE-2023-22644.
- What are the consequences of CWE-1270?
- Exploiting CWE-1270 can lead to: Modify Files or Directories, Execute Unauthorized Code or Commands, Bypass Protection Mechanism, Gain Privileges or Assume Identity, Read Memory, Modify Memory.
- Is CWE-1270 actively exploited?
- 5 recorded CVEs are caused by CWE-1270; none are currently in CISA's KEV catalog of actively exploited flaws.
References
- MITRE CWE definition (CWE-1270) (opens in a new tab)
- CWE-1270 vulnerabilities on NVD (opens in a new tab)
- Learn: What is a CWE?
Weakness data is sourced from the MITRE CWE catalog (v4.20). CVE associations are aggregated and kept current by RadicalNotion.AI.
Stay ahead of CWE-1270
Get alerted the moment a new CWE-1270 vulnerability affects your stack, with AI-written analysis, severity context, and remediation guidance.