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
+ Applicable Platforms



+ Potential Mitigations

Use a non-conflicting privilege scheme.

Use synchronization when locking a resource.

+ Relationships
NatureTypeIDNameView(s) this relationship pertains toView(s)
ChildOfCategoryCategory411Resource Locking Problems
Development Concepts (primary)699
ChildOfWeakness BaseWeakness Base667Insufficient Locking
Research Concepts (primary)1000
ParentOfWeakness VariantWeakness Variant591Sensitive Data Storage in Improperly Locked Memory
Development Concepts (primary)699
Research Concepts (primary)1000
+ Taxonomy Mappings
Mapped Taxonomy NameNode IDFitMapped Node Name
PLOVERInsufficient Resource Locking
+ Content History
Submission DateSubmitterOrganizationSource
PLOVERExternally Mined
Modification DateModifierOrganizationSource
2008-07-01Eric DalciCigitalExternal
updated Potential Mitigations, Time of Introduction
2008-09-08CWE Content TeamMITREInternal
updated Relationships, Taxonomy Mappings