| Name |
Exploitation of Improperly Controlled Hardware Security Identifiers |
|
| Likelyhood of attack |
Typical severity |
| Medium |
Very High |
|
| Summary |
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. |
| Prerequisites |
Awareness of the hardware being leveraged. Access to the hardware being leveraged. |
| Solutions | Review generation of security identifiers for design inconsistencies and common weaknesses. Review security identifier decoders for design inconsistencies and common weaknesses. Test security identifier definition, access, and programming flow in both pre-silicon and post-silicon environments. |
| Related Weaknesses |
|
CWE ID
|
Description
|
| CWE-1259 |
Improper Restriction of Security Token Assignment |
| CWE-1267 |
Policy Uses Obsolete Encoding |
| CWE-1270 |
Generation of Incorrect Security Tokens |
| CWE-1294 |
Insecure Security Identifier Mechanism |
| CWE-1302 |
Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC) |
|
| Related CAPECS |
|
CAPEC ID
|
Description
|
| CAPEC-1 |
In applications, particularly web applications, access to functionality is mitigated by an authorization framework. This framework maps Access Control Lists (ACLs) to elements of the application's functionality; particularly URL's for web apps. In the case that the administrator failed to specify an ACL for a particular element, an attacker may be able to access it with impunity. An attacker with the ability to access functionality not properly constrained by ACLs can obtain sensitive information and possibly compromise the entire application. Such an attacker can access resources that must be available only to users at a higher privilege level, can access management sections of the application, or can run queries for data that they otherwise not supposed to. |
| CAPEC-180 |
An attacker exploits a weakness in the configuration of access controls and is able to bypass the intended protection that these measures guard against and thereby obtain unauthorized access to the system or network. Sensitive functionality should always be protected with access controls. However configuring all but the most trivial access control systems can be very complicated and there are many opportunities for mistakes. If an attacker can learn of incorrectly configured access security settings, they may be able to exploit this in an attack. |
|