|
|
|
|
CWE-414: Missing Lock Check| Weakness ID: 414 (Weakness Base) | | Status: Draft |
 Description
Description Summary A product does not check to see if a lock is present before performing sensitive operations on a resource.
Time of Introduction
- Architecture and Design
- Implementation
Common Consequences | Scope | Effect |
|---|
Integrity Availability | Technical Impact: Modify application
data; DoS: instability; DoS: crash / exit /
restart |
Observed Examples | Reference | Description |
|---|
| CVE-2004-1056 | Product does not properly check if a lock is
present, allowing other attackers to access
functionality. |
Potential Mitigations
Implement a reliable lock mechanism. |
Relationships Taxonomy Mappings | Mapped Taxonomy Name | Node ID | Fit | Mapped Node Name |
|---|
| PLOVER | | | Missing Lock Check |
Content History | Submissions |
|---|
| Submission Date | Submitter | Organization | Source |
|---|
| PLOVER | | Externally Mined | | | Modifications |
|---|
| Modification Date | Modifier | Organization | Source |
|---|
| 2008-07-01 | Eric Dalci | Cigital | External | | updated Potential_Mitigations,
Time_of_Introduction | | 2008-09-08 | CWE Content Team | MITRE | Internal | | updated Relationships,
Taxonomy_Mappings | | 2011-06-01 | CWE Content Team | MITRE | Internal | | updated Common_Consequences |
|
