COMMON WEAKNESS ENUMERATIONIncomplete

CWE-1294

Insecure Security Identifier Mechanism

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.

Abstraction

Class

Structure

Simple

Likelihood of Exploit

Medium

Understand the problem

What is the problem?

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.

Root cause

How and when does the problem arise?

Lifecycle phase

Architecture and Design

Such issues could be introduced during hardware architecture and design, then identified later during Testing or System Configuration phases.

Lifecycle phase

Implementation

Such issues could be introduced during hardware implementation, then identified later during Testing or System Configuration phases.

Risk

What does successful exploitation lead to?

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

Affected security scopes: Confidentiality, Integrity, Availability, Access Control

Defence

How is it prevented and fixed?

Architecture and Design

Architecture and design approach

Detail
Security Identifier Decoders must be reviewed for design inconsistency and common weaknesses.

Implementation

Implementation-phase defence

Detail
Access and programming flows must be tested in pre-silicon and post-silicon testing.
CWE-1294: Common Weakness Enumeration Entry CWE-1294 · DayBreach Sözlük · DayBreach