CWE-1270: Generation of Incorrect Security Tokens

Extended Description

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.

Code Examples & CVEs

Demonstrative Examples

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.

Assume the system has two agents: a Main-controller and an Aux-controller. The respective Security Tokens are "1" and "2". Register Description Default AES_ENC_DEC_KEY_0 AES key [0:31] for encryption or decryption 0x00000000 AES_ENC_DEC_KEY_1 AES key [32:63] for encryption or decryption 0x00000000 AES_ENC_DEC_KEY_2 AES key [64:95] for encryption or decryption 0x00000000 AES_ENC_DEC_KEY_3 AES key [96:127] for encryption or decryption 0x00000000 AES_KEY_ACCESS_POLICY AES key access register [31:0] 0x00000002

BadOther

The SoC incorrectly generates Security Token "1" for every agent. In other words, both Main-controller and Aux-controller are assigned Security Token "1".

GoodOther

The SoC should correctly generate Security Tokens, assigning "1" to the Main-controller and "2" to the Aux-controller

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-1270 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-1270, Generation of Incorrect Security Tokens, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Address Generation of Incorrect Security Tokens during Architecture and Design

MITRE associates mitigation with Architecture and Design, and Implementation; recorded impacts include Modify Files or Directories, Execute Unauthorized Code or Commands, Bypass Protection Mechanism, Gain Privileges or Assume Identity, and Read Memory; the entry maps to CAPEC-121, CAPEC-633, and CAPEC-681. Use these source-defined anchors to turn CWE-1270 into implementation, review, and verification checks for the affected component.

CWE-1270: Generation of Incorrect Security Tokens — MITRE CWE

Triage CWE-1270 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-1270, Generation of Incorrect Security Tokens, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-1270

Apply MITRE's full root-cause mapping guidance when using CWE-1270, Generation of Incorrect Security Tokens. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-1270 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-1270, Generation of Incorrect Security Tokens. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-1270: Generation of Incorrect Security Tokens?+

CWE-1270: Generation of Incorrect Security Tokens is a Common Weakness Enumeration (CWE) entry maintained by MITRE. 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.

What are the security consequences of Generation of Incorrect Security Tokens?+

If exploited, CWE-1270 (Generation of Incorrect Security Tokens) it can compromise Confidentiality, Integrity, Availability and Access Control, leading to outcomes such as Modify Files or Directories, Execute Unauthorized Code or Commands, Bypass Protection Mechanism, Gain Privileges or Assume Identity, Read Memory and Modify Memory.

How do you prevent or mitigate Generation of Incorrect Security Tokens?+

Recommended mitigations for CWE-1270 include: 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.

Which programming languages are affected by Generation of Incorrect Security Tokens?+

CWE-1270 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-1270 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

CWE-1270: Generation of Incorrect Security Tokens

Extended Description

Technical Details

Applicable To

Security Consequences

Scope

Impact

Likelihood

Mitigation Strategies

Phase

Description

Detection Methods