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

CWE-412CWE-567CWE-662CWE-667CWE-833CWE-1322

MITRE ATT&CK crosswalk· 1

T1499.004: Endpoint Denial of Service: Application or System Exploitation

Exploits6

TypeTargetConfidenceTier
WeaknessUnsynchronized Access to Shared Data in a Multithreaded Contextcwe-567100%live
WeaknessImproper Lockingcwe-667100%live
WeaknessImproper Synchronizationcwe-662100%live
WeaknessUse of Blocking Code in Single-threaded, Non-blocking Contextcwe-1322100%live
WeaknessDeadlockcwe-833100%live
WeaknessUnrestricted Externally Accessible Lockcwe-412100%live

Related to1

TypeTargetConfidenceTier
SubTechniqueApplication or System Exploitationt1499.004100%live

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CAPEC
Blockage
CAPEC
Obstruction
CAPEC
Leveraging Race Conditions
CAPEC
Force Use of Corrupted Files
CAPEC
Software Integrity Attack
CAPEC
IP Address Blocking
Sourced from MITRE CAPEC. Curated by Adam Lundqvist, SQUR.