Einführungsmodi
Architecture and Design
Anwendbare Plattformen
Sprache
Class: Not Language-Specific (Undetermined)
Technologien
Class: System on Chip (Undetermined)
Häufige Konsequenzen
| Bereich |
Auswirkung |
Wahrscheinlichkeit |
| Access Control | Bypass Protection Mechanism
Note: An untrusted component can master transactions on the HW bus and target memory or other assets to compromise the SoC boot firmware. | High |
Mögliche Gegenmaßnahmen
Phases : Architecture and Design
Hinweise zur Schwachstellen-Zuordnung
Begründung : This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Kommentar : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
Verwandte Angriffsmuster
| CAPEC-ID |
Name des Angriffsmusters |
| CAPEC-1 |
Accessing Functionality Not Properly Constrained by ACLs
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 |
Exploiting Incorrectly Configured Access Control Security Levels
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. |
Referenzen
REF-1130
Intel x86 Root of Trust: loss of trust
Mark Ermolov, Positive Technologies.
https://blog.ptsecurity.com/2020/03/intelx86-root-of-trust-loss-of-trust.html REF-1042
Owned by an iPod
Maximillian Dornseif.
https://web.archive.org/web/20060505224959/https://pacsec.jp/psj04/psj04-dornseif-e.ppt
Einreichung
| Name |
Organisation |
Datum |
Veröffentlichungsdatum |
Version |
| Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi |
Intel Corporation |
2019-10-15 +00:00 |
2020-02-24 +00:00 |
4.0 |
Änderungen
| Name |
Organisation |
Datum |
Kommentar |
| CWE Content Team |
MITRE |
2020-08-20 +00:00 |
updated References, Related_Attack_Patterns |
| CWE Content Team |
MITRE |
2023-04-27 +00:00 |
updated References, Relationships |
| CWE Content Team |
MITRE |
2023-06-29 +00:00 |
updated Mapping_Notes |
| CWE Content Team |
MITRE |
2025-12-11 +00:00 |
updated Applicable_Platforms, Time_of_Introduction, Weakness_Ordinalities |