A product does not check to see if a lock is present before performing sensitive operations on a resource.
| Nature | Mapping | Type | ID | Name |
|---|
| Nature | Mapping | Type | ID | Name |
|---|
| Nature | Mapping | Type | ID | Name |
|---|
| Scope | Likelihood | Impact | Note |
|---|---|---|---|
| IntegrityAvailability | N/A | Modify Application DataDoS: InstabilityDoS: Crash, Exit, or Restart | N/A |
Implement a reliable lock mechanism.
N/A
N/A
| Reference | Description |
|---|---|
| CVE-2004-1056 | Product does not properly check if a lock is present, allowing other attackers to access functionality. |
| 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 |
|---|---|---|---|
| PLOVER | N/A | N/A | Missing Lock Check |
| Software Fault Patterns | SFP19 | N/A | Missing Lock |
| ID | Name |
|---|