Description
The System-on-Chip (SoC) implements a Security Identifier mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. However, the Security Identifiers are not correctly implemented.
Systems-On-Chip (Integrated circuits and hardware engines) implement Security Identifiers to differentiate/identify actions originated from various agents. These actions could be 'read', 'write', 'program', 'reset', 'fetch', 'compute', etc. Security identifiers are generated and assigned to every agent in the System (SoC) that is either capable of generating an action or receiving an action from another agent. Every agent could be assigned a unique, Security Identifier based on its trust level or privileges. A broad class of flaws can exist in the Security Identifier process, including but not limited to missing security identifiers, improper conversion of security identifiers, incorrect generation of security identifiers, etc.
Potential Impact
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
Mitigations & Prevention
Security Identifier Decoders must be reviewed for design inconsistency and common weaknesses.
Access and programming flows must be tested in pre-silicon and post-silicon testing.
Related Weaknesses
Frequently Asked Questions
What is CWE-1294?
CWE-1294 (Insecure Security Identifier Mechanism) is a software weakness identified by MITRE's Common Weakness Enumeration. It is classified as a Class-level weakness. The System-on-Chip (SoC) implements a Security Identifier mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. However, the Security Identifi...
How can CWE-1294 be exploited?
Attackers can exploit CWE-1294 (Insecure Security Identifier Mechanism) to modify memory, read memory, dos: resource consumption (other), execute unauthorized code or commands, gain privileges or assume identity, quality degradation. This weakness is typically introduced during the Architecture and Design, Implementation phase of software development.
How do I prevent CWE-1294?
Key mitigations include: Security Identifier Decoders must be reviewed for design inconsistency and common weaknesses.
What is the severity of CWE-1294?
CWE-1294 is classified as a Class-level weakness (High abstraction). Its actual severity depends on the specific context and how the weakness manifests in your application.