| Nature | Type | ID | Name |
|---|
The adversary initiates an exploratory phase to get familiar with the system.
The adversary initiates an exploratory phase to get familiar with the system.
| Technique |
|---|
The adversary triggers a first action (such as holding a resource) and initiates a second action which will wait for the first one to finish.
The adversary triggers a first action (such as holding a resource) and initiates a second action which will wait for the first one to finish.
| Technique |
|---|
If the target program has a deadlock condition, the program waits indefinitely resulting in a denial of service.
If the target program has a deadlock condition, the program waits indefinitely resulting in a denial of service.
| Technique |
|---|
This type of attack may be sophisticated and require knowledge about the system's resources and APIs.
| Scope | Likelihood | Impact | Note |
|---|---|---|---|
| Availability | N/A | Resource Consumption | A successful forced deadlock attack compromises the availability of the system by exhausting its available resources. |
| ID | Name |
|---|---|
| CWE-1322 | Use of Blocking Code in Single-threaded, Non-blocking Context |
| CWE-412 | Unrestricted Externally Accessible Lock |
| CWE-567 | Unsynchronized Access to Shared Data in a Multithreaded Context |
| CWE-662 | Improper Synchronization |
| CWE-667 | Improper Locking |
| CWE-833 | Deadlock |
| Taxonomy Name | Entry ID | Entry Name |
|---|---|---|
| ATTACK | 1499.004 | Endpoint Denial of Service: Application or System Exploitation |