CWEweakness

CWE-1294 Insecure Security Identifier Mechanism

Official page ↗
Abstraction
Class
Structure
Simple
Status
Incomplete
Languages
Not Language-Specific
CWE version
5.0

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.

Common consequences

• 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

Potential mitigations

• [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.

Related

Attack pattern · CAPEC (2)

  • CAPEC-121 Exploit Non-Production Interfaces attack pattern
  • CAPEC-681 Exploitation of Improperly Controlled Hardware Security Identifiers attack pattern

Child of · CWE (1)

  • CWE-284 Improper Access Control weakness

Referenced by CAPEC · weakness (2)

  • CAPEC-121 Exploit Non-Production Interfaces attack pattern
  • CAPEC-681 Exploitation of Improperly Controlled Hardware Security Identifiers attack pattern

Referenced by CVE · weakness (1)

  • CVE-2026-24084 Weak configuration when UE does not verify the consistency of its additional security capabilities with the replayed capabilities. vulnerability

Referenced by CWE · child of (5)

  • CWE-1259 Improper Restriction of Security Token Assignment weakness
  • CWE-1270 Generation of Incorrect Security Tokens weakness
  • CWE-1290 Incorrect Decoding of Security Identifiers weakness
  • CWE-1292 Incorrect Conversion of Security Identifiers weakness
  • CWE-1302 Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC) weakness