Metalikelihood: Lowseverity: HighStable
CAPEC-25Forced Deadlock
Abstraction
Meta
Status
Stable
Likelihood
Low
Severity
High
Description
The adversary triggers and exploits a deadlock condition in the target software to cause a denial of service. A deadlock can occur when two or more competing actions are waiting for each other to finish, and thus neither ever does. Deadlock conditions can be difficult to detect.
Metadata: meta CAPEC pattern, status stable, likelihood low, severity high. Underlying weaknesses: CWE-412, CWE-567, CWE-662, CWE-667, CWE-833 (and 1 more). Mapped ATT&CK technique: [object Object].
Related weaknesses· 6
MITRE ATT&CK crosswalk· 1
Exploits6
| Type | Target | Confidence | Tier |
|---|---|---|---|
| Weakness | Unsynchronized Access to Shared Data in a Multithreaded Contextcwe-567 | 100% | live |
| Weakness | Improper Lockingcwe-667 | 100% | live |
| Weakness | Improper Synchronizationcwe-662 | 100% | live |
| Weakness | Use of Blocking Code in Single-threaded, Non-blocking Contextcwe-1322 | 100% | live |
| Weakness | Deadlockcwe-833 | 100% | live |
| Weakness | Unrestricted Externally Accessible Lockcwe-412 | 100% | live |
Related to1
| Type | Target | Confidence | Tier |
|---|---|---|---|
| SubTechnique | Application or System Exploitationt1499.004 | 100% | live |
Related by meaning· 6
Nearest entities by semantic similarity across the cs-graph corpus.