CAPEC-124
Shared Resource Manipulation
Mittel
Draft
2014-06-23
00h00 +00:00
00h00 +00:00
2020-12-17
00h00 +00:00
00h00 +00:00
Benachrichtigung für ein CAPEC
Bleiben Sie über alle Änderungen zu einem bestimmten CAPEC informiert.
CAPEC-Beschreibungen
An adversary exploits a resource shared between multiple applications, an application pool or hardware pin multiplexing to affect behavior. Resources may be shared between multiple applications or between multiple threads of a single application. Resource sharing is usually accomplished through mutual access to a single memory location or multiplexed hardware pins. If an adversary can manipulate this shared resource (usually by co-opting one of the applications or threads) the other applications or threads using the shared resource will often continue to trust the validity of the compromised shared resource and use it in their calculations. This can result in invalid trust assumptions, corruption of additional data through the normal operations of the other users of the shared resource, or even cause a crash or compromise of the sharing applications.
CAPEC-Informationen
Voraussetzungen
The target applications, threads or functions must share resources between themselves.The adversary must be able to manipulate some piece of the shared resource either directly or indirectly and the other users of the data must accept the changed data as valid. Usually this requires that the adversary be able to compromise one of the sharing applications or threads in order to manipulate the shared data.
Erforderliche Ressourcen
None: The attacker does not need any specialized resources to execute this type of attack.Verwandte Schwachstellen
| Name der Schwachstelle | |
|---|---|
CWE-1189 |
Improper Isolation of Shared Resources on System-on-a-Chip (SoC) The System-On-a-Chip (SoC) does not properly isolate shared resources between trusted and untrusted agents. |
CWE-1331 |
Improper Isolation of Shared Resources in Network On Chip (NoC) The Network On Chip (NoC) does not isolate or incorrectly isolates its on-chip-fabric and internal resources such that they are shared between trusted and untrusted agents, creating timing channels. |
Einreichung
| Name | Organisation | Datum | Veröffentlichungsdatum |
|---|---|---|---|
| CAPEC Content Team | The MITRE Corporation |
Änderungen
| Name | Organisation | Datum | Kommentar |
|---|---|---|---|
| CAPEC Content Team | The MITRE Corporation | Updated Description Summary, Related_Attack_Patterns | |
| CAPEC Content Team | The MITRE Corporation | Updated Attack_Prerequisites, Description Summary, Resources_Required | |
| CAPEC Content Team | The MITRE Corporation | Updated Related_Weaknesses | |
| CAPEC Content Team | The MITRE Corporation | Updated @Name, Description, Prerequisites, Related_Weaknesses, Resources_Required | |
| CAPEC Content Team | The MITRE Corporation | Updated Related_Weaknesses |
