CWE-1270: Generation of Incorrect Security Tokens

What is CWE-1270?

CWE-1270 is Generation of Incorrect Security Tokens. The flaw arises when The product implements a Security Token mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. The database currently holds 3 vulnerabilities mapped to CWE-1270 and none of them are in the CISA Known Exploited Vulnerabilities catalog.

OWASP Top 10 Rank-
Related CVES (365 days)3
AbstractionBase
Likelihood of exploit-

Vulnerabilities mapped to CWE-1270

3 vulnerabilities

No data

No vulnerability data in CISA KEV for CWE-1270

Official definition

ByMitre CWE

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.

Characteristics

Modes of introduction

  • Architecture and Design
  • Implementation

Common consequences

ImpactScopeExplanation
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 RestartConfidentiality, Integrity, Availability, Access ControlIncorrectly 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.

Risk mitigations

  1. Architecture and Design, Implementation- 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.
Sources (2)
MITRE CWE
CWE Terms of Use

CWE™ Program, operated by The MITRE Corporation. Copyright © 2006–2026, The MITRE Corporation. The MITRE Corporation hereby grants you a non-exclusive, royalty-free license to use CWE for research, development, and commercial purposes. CWE Terms of Use.

Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.

Explore CyStack VulnScan
More resources & insights

Explore more resources from CyStack

Website security reports

Review CyStack's security rating and practical recommendations for websites and edge assets.

Learn more

CyStack research

Explore cybersecurity research from our team of security specialists.

Learn more

Cybersecurity knowledge

Browse practical cybersecurity knowledge across CyStack's articles and guides.

Learn more