Insecure Security Identifier Mechanism

Incomplete Class
Structure: Simple
Description

This vulnerability occurs when a System-on-Chip (SoC) implements a Security Identifier mechanism to control transaction permissions, but the implementation contains flaws that undermine its security.

Extended Description

In a System-on-Chip, Security Identifiers act like digital ID badges for every hardware agent (like processors or engines). Each agent gets a unique identifier based on its trust level, which determines what actions it can perform—such as read, write, program, or reset. These identifiers are essential for enforcing security boundaries between different parts of the chip. A wide range of implementation errors can break this security model. Common issues include agents missing identifiers entirely, incorrect generation of identifier values, or improper conversion between identifier formats. These flaws allow unauthorized agents to bypass access controls, potentially leading to data theft, privilege escalation, or system compromise.

Common Consequences 1
Scope: ConfidentialityIntegrityAvailabilityAccess Control

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

Potential Mitigations 2
Phase: Architecture and Design
Security Identifier Decoders must be reviewed for design inconsistency and common weaknesses.
Phase: Implementation
Access and programming flows must be tested in pre-silicon and post-silicon testing.
Applicable Platforms
Languages:
Not Language-Specific : Undetermined
Technologies:
Bus/Interface Hardware : UndeterminedNot Technology-Specific : Undetermined
Modes of Introduction
Architecture and Design
Implementation
Related Weaknesses
Notes
MaintenanceThis entry is still under development and will continue to see updates and content improvements.