CWE-1294

Insecure Security Identifier Mechanism

ClassIncompleteSimple1 CVE

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.

Extended description

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.

Common consequences1

ConfidentialityIntegrityAvailabilityAccess ControlModify MemoryRead MemoryDoS: Resource Consumption (Other)Execute Unauthorized Code or CommandsGain Privileges or Assume IdentityQuality Degradation

Potential mitigations2

Architecture and Design
Security Identifier Decoders must be reviewed for design inconsistency and common weaknesses.
Implementation
Access and programming flows must be tested in pre-silicon and post-silicon testing.

Relationships1

ChildOfCWE-284

CVEs referencing this CWE1

CVE	Description	Severity	EPSS	Flags	Modified
CVE-2026-24084	Weak configuration when UE does not verify the consistency of its additional security capabilities with the replayed capabilities.	HIGH7.5	no EPSS		2026-08-04