CAPEC-681: Exploitation of Improperly Controlled Hardware Security Identifiers
Description
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.
Severity :
Very High
Possibility :
Medium
Type :
Detailed
Relationships with other CAPECs
This table shows the other attack patterns and high level categories that are related to this attack pattern.
Prerequisites
This table shows the other attack patterns and high level categories that are related to this attack pattern.
- Awareness of the hardware being leveraged.
- Access to the hardware being leveraged.
Skills required
This table shows the other attack patterns and high level categories that are related to this attack pattern.
- Medium Ability to execute actions within the SoC.
- High Intricate knowledge of the identifiers being utilized.
Taxonomy mappings
Mappings to ATT&CK, OWASP and other frameworks.
Related CWE
A Related Weakness relationship associates a weakness with this attack pattern. Each association implies a weakness that must exist for a given attack to be successful.
Visit http://capec.mitre.org/ for more details.