COMMON ATTACK PATTERN ENUMERATION AND CLASSIFICATIONLive MITRE record

CAPEC-681

Exploitation of Improperly Controlled Hardware Security Identifiers

An adversary takes advantage of missing or incorrectly configured security identifiers (e.g., tokens), which are used for access control within a System-on-Chip (SoC), to read/write data or execute a given action.

Abstraction

Detailed

Typical severity

Very High

Likelihood of attack

Medium

Understand the attack

What is this attack pattern?

An adversary takes advantage of missing or incorrectly configured security identifiers (e.g., tokens), which are used for access control within a System-on-Chip (SoC), to read/write data or execute a given action.

Extended description

A System-on-Chip (SoC) often implements a security identifier mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. However, these mechanisms may be exploitable due to any number of the following: The security identifiers are missing The security identifiers are incorrectly implemented or generated The security identifiers are generated with an obsolete encoding The security identifiers are generated and implemented correctly, but are improperly protected If the security identifiers leveraged by the SoC are missing or misconfigured, an adversary may be able to take advantage of this shortcoming to circumvent the intended access controls. This could result in the adversary gaining unintended access, performing a Denial of Service (DoS), escalating privileges, or spoofing actions from a trusted agent.

Requirements

What does the attack require?

Prerequisites

  • Awareness of the hardware being leveraged.
  • Access to the hardware being leveraged.

Skills required

  • Medium: Ability to execute actions within the SoC.
  • High: Intricate knowledge of the identifiers being utilized.

Resources required

Not stated in the MITRE record.

Impact

What does a successful attack lead to?

Modify Data

Affected scopes: Integrity

Read Data

Affected scopes: Confidentiality

Gain Privileges

Affected scopes: Confidentiality, Access Control, Authorization

Defence

How is it prevented and mitigated?

1
Review generation of security identifiers for design inconsistencies and common weaknesses.
2
Review security identifier decoders for design inconsistencies and common weaknesses.
3
Test security identifier definition, access, and programming flow in both pre-silicon and post-silicon environments.

Real world

MITRE example instances

Example instance 1Detail
A system contains a register (divided into four 32-bit registers) that is used to store a 128-bit AES key for encryption/decryption, in addition to an access-policy register. The access-policy register determines which agents may access the AES-key registers, based on a corresponding security identifier. It is assumed the system has two agents: a Main-controller and an Aux-controller, with respective security identifiers "1" and "2". The Main-controller (ID "1") is meant to have access to the AES-key registers, while the Aux-controller (ID "2") has access to the access-policy register. If a SoC incorrectly generates security identifier "1" for both agents, then both agents will have access to the AES-key registers. This could further result in a Denial-of-Service (DoS) or the execution of an action that in turn could result in privilege escalation or unintended access.
CAPEC-681: Exploitation of Improperly Controlled Hardware Security Identifiers — DayBreach Saldırı Sözlüğü · DayBreach