CWE-413: Insufficient Resource Locking
Insufficient Resource Locking
Weakness ID: 413 (Weakness Base) Status: Draft
Description
Description Summary
A product does not sufficiently lock resources, in a way that
either (1) allows an attacker to simultaneously access those resources, or (2)
causes other errors that lead to a resultant weakness.
Time of Introduction
Architecture and Design
Implementation
Potential Mitigations
Phase Description
Use a non-conflicting privilege scheme.
Use synchronization when locking a resource.
Relationships
Taxonomy Mappings
Mapped Taxonomy Name Node ID Fit Mapped Node Name
PLOVER Insufficient Resource Locking
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