The product contains multiple threads or executable segments that are waiting for each other to release a necessary lock, resulting in deadlock.
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| ChildOf | Allowed-with-Review | C | 667 | Improper Locking |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | C | 411 | Resource Locking Problems |
| MemberOf | Prohibited | C | 853 | The CERT Oracle Secure Coding Standard for Java (2011) Chapter 10 - Locking (LCK) |
| MemberOf | Prohibited | C | 1401 | Comprehensive Categorization: Concurrency |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | BS | BOSS-314 | DoS: Resource Consumption (CPU) (impact) |
| MemberOf | Prohibited | BS | BOSS-324 | DoS: Crash, Exit, or Restart (impact) |
| MemberOf | Prohibited | BS | BOSS-333 | DoS: Resource Consumption (Other) (impact) |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | C | 411 | Resource Locking Problems |
| Scope | Likelihood | Impact | Note |
|---|---|---|---|
| Availability | N/A | DoS: Resource Consumption (CPU)DoS: Resource Consumption (Other)DoS: Crash, Exit, or Restart | Each thread of execution will "hang" and prevent tasks from completing. In some cases, CPU consumption may occur if a lock check occurs in a tight loop. |
Each thread of execution will "hang" and prevent tasks from completing. In some cases, CPU consumption may occur if a lock check occurs in a tight loop.
| Reference | Description |
|---|---|
| CVE-1999-1476 | A bug in some Intel Pentium processors allow DoS (hang) via an invalid "CMPXCHG8B" instruction, causing a deadlock |
| CVE-2009-2857 | OS deadlock |
| CVE-2009-1961 | OS deadlock involving 3 separate functions |
| CVE-2009-2699 | deadlock in library |
| CVE-2009-4272 | deadlock triggered by packets that force collisions in a routing table |
| CVE-2002-1850 | read/write deadlock between web server and script |
| CVE-2004-0174 | web server deadlock involving multiple listening connections |
| CVE-2009-1388 | multiple simultaneous calls to the same function trigger deadlock. |
| CVE-2006-5158 | chain: other weakness leads to NULL pointer dereference (CWE-476) or deadlock (CWE-833). |
| CVE-2006-4342 | deadlock when an operation is performed on a resource while it is being removed. |
| CVE-2006-2374 | Deadlock in device driver triggered by using file handle of a related device. |
| CVE-2006-2275 | Deadlock when large number of small messages cannot be processed quickly enough. |
| CVE-2005-3847 | OS kernel has deadlock triggered by a signal during a core dump. |
| CVE-2005-3106 | Race condition leads to deadlock. |
| CVE-2005-2456 | Chain: array index error (CWE-129) leads to deadlock (CWE-833) |
| Ordinality | Description |
|---|
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.
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.
| Taxonomy Name | Entry ID | Fit | Entry Name |
|---|---|---|---|
| The CERT Oracle Secure Coding Standard for Java (2011) | LCK08-J | N/A | Ensure actively held locks are released on exceptional conditions |