Insecure Security Identifier Mechanism

Opis

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.

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.

Skutki

• 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

Zapobieganie

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

Słabość nadrzędna

• CWE-284 Improper Access Control

Słabości podrzędne

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

Kiedy powstaje

• Architecture and Design — Such issues could be introduced during hardware architecture and design, then identified later during Testing or System Configuration phases.
• Implementation — Such issues could be introduced during hardware implementation, then identified later during Testing or System Configuration phases.

Dotyczy

Not Language-Specific, Not OS-Specific, Not Architecture-Specific, Bus/Interface Hardware, Not Technology-Specific

Uwagi

This entry is still under development and will continue to see updates and content improvements.