2143
The product implements a decoding mechanism to decode certain bus-transaction signals to
security identifiers. If the decoding is implemented incorrectly, then untrusted agents can now gain
unauthorized access to the asset.
Extended Description
In a System-On-Chip (SoC), various integrated circuits and hardware engines generate
transactions such as to access (reads/writes) assets or perform certain actions (e.g., reset, fetch,
compute, etc.). Among various types of message information, a typical transaction is comprised
of source identity (to identify the originator of the transaction) and a destination identity (to route
the transaction to the respective entity). Sometimes the transactions are qualified with a security
identifier. The security identifier helps the destination agent decide on the set of allowed actions
(e.g., access an asset for read and writes). A decoder decodes the bus transactions to map
security identifiers into necessary access-controls/protections.
A common weakness that can exist in this scenario is incorrect decoding because an untrusted
agent's security identifier is decoded into a trusted agent's security identifier. Thus, an untrusted
agent previously without access to an asset can now gain access to the asset.
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 : Bus/Interface Hardware (Prevalence = Undetermined)
Technology : Not Technology-Specific (Prevalence = Undetermined)
Common Consequences
Scope Impact Likelihood
Confidentiality
Integrity
Availability
Access Control
Modify Memory
Read Memory
DoS: Resource Consumption (Other)
Execute Unauthorized Code or Commands
Gain Privileges or Assume Identity
Quality Degradation
High
Potential Mitigations
Phase: Architecture and Design
Security identifier decoders must be reviewed for design consistency and common weaknesses.
Phase: Implementation
CWE Version 4.14
CWE-1290: Incorrect Decoding of Security Identifiers
CWE-1290: Incorrect Decoding of Security Identifiers