COMMON WEAKNESS ENUMERATIONDraft

CWE-1192

Improper Identifier for IP Block used in System-On-Chip (SOC)

The System-on-Chip (SoC) does not have unique, immutable identifiers for each of its components.

Abstraction

Base

Structure

Simple

Likelihood of Exploit

Medium

Understand the problem

What is the problem?

The System-on-Chip (SoC) does not have unique, immutable identifiers for each of its components.

Extended description

A System-on-Chip (SoC) comprises several components (IP) with varied trust requirements. It is required that each IP is identified uniquely and should distinguish itself from other entities in the SoC without any ambiguity. The unique secured identity is required for various purposes. Most of the time the identity is used to route a transaction or perform certain actions, including resetting, retrieving a sensitive information, and acting upon or on behalf of something else. There are several variants of this weakness: - A "missing" identifier is when the SoC does not define any mechanism to uniquely identify the IP. - An "insufficient" identifier might provide some defenses - for example, against the most common attacks - but it does not protect against everything that is intended. - A "misconfigured" mechanism occurs when a mechanism is available but not implemented correctly. - An "ignored" identifier occurs when the SoC/IP has not applied any policies or does not act upon the identifier securely.

Root cause

How and when does the problem arise?

Lifecycle phase

Architecture and Design

Lifecycle phase

Implementation

Lifecycle phase

Operation

Risk

What does successful exploitation lead to?

Bypass Protection Mechanism

Affected security scopes: Access Control

Defence

How is it prevented and fixed?

Architecture and Design

Separation of Privilege

Detail
Every identity generated in the SoC should be unique and immutable in hardware. The actions that an IP is trusted or not trusted should be clearly defined, implemented, configured, and tested. If the definition is implemented via a policy, then the policy should be immutable or protected with clear authentication and authorization.
CWE-1192: Common Weakness Enumeration Entry CWE-1192 · DayBreach Sözlük · DayBreach