2101
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.
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. 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 Denialof-
Service (DoS) or the execution of an action that in turn could result in privilege escalation or
unintended access.
Relationships
The table(s) below shows the weaknesses and high level categories that are related to this
weakness. These relationships are defined as ChildOf, ParentOf, MemberOr and give insight to
similar items that may exist at higher and lower levels of abstraction. In addition, relationships such
as PeerOf and CanAlsoBe are defined to show similar weaknesses that may want to be explored.
Relevant to the view "Research Concepts" (CWE-1000)
Nature Type ID Name Page
ChildOf 284 Improper Access Control 680
Relevant to the view "Hardware Design" (CWE-1194)
Nature Type ID Name Page
ChildOf 1294 Insecure Security Identifier Mechanism 2150
Applicable Platforms
Language : Not Language-Specific (Prevalence = Undetermined)
Operating_System : Not OS-Specific (Prevalence = Undetermined)
Architecture : Not Architecture-Specific (Prevalence = Undetermined)
Technology : Not Technology-Specific (Prevalence = Undetermined)
Common Consequences
Scope Impact Likelihood
Confidentiality
Integrity
Availability
Access Control
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
High
Potential Mitigations
Phase: Architecture and Design
Phase: 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.
Demonstrative Examples
CWE Version 4.14
CWE-1271: Uninitialized Value on Reset for Registers Holding Security Settings
CWE-1271: Uninitialized Value on Reset for Registers Holding Security Settings