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.
View on MITREExtended 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. 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.
Technical Details
- Structure
- Simple
Applicable To
Security Consequences
Scope
Impact
Likelihood
HighMitigation Strategies
Phase
Description
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.
Detection Methods
No detection method information available for this CWE.
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
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
CWE Relationships
No relationship information available for this 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. 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.
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.