1007
Mapped Taxonomy Name Node ID Fit Mapped Node Name
The CERT Oracle Secure
Coding Standard for Java
(2011)
VNA02-J Ensure that compound operations on
shared variables are atomic
The CERT Oracle Secure
Coding Standard for Java
(2011)
LCK00-J Use private final lock objects to
synchronize classes that may interact
with untrusted code
Software Fault Patterns SFP19 Missing Lock
CWE-414: Missing Lock Check
Weakness ID : 414
Structure : Simple
Abstraction : Base
Description
A product does not check to see if a lock is present before performing sensitive operations on a
resource.
Relationships
The table(s) below shows the weaknesses and high level categories that are related to this
weakness. These relationships are defined as ChildOf, ParentOf, MemberOr and give insight to
similar items that may exist at higher and lower levels of abstraction. In addition, relationships such
as PeerOf and CanAlsoBe are defined to show similar weaknesses that may want to be explored.
Relevant to the view "Research Concepts" (CWE-1000)
Nature Type ID Name Page
ChildOf 667 Improper Locking 1464
Relevant to the view "Software Development" (CWE-699)
Nature Type ID Name Page
MemberOf 411 Resource Locking Problems 2325
Applicable Platforms
Language : Not Language-Specific (Prevalence = Undetermined)
Common Consequences
Scope Impact Likelihood
Integrity
Availability
Modify Application Data
DoS: Instability
DoS: Crash, Exit, or Restart
Potential Mitigations
Phase: Architecture and Design
Phase: Implementation
Implement a reliable lock mechanism.
Observed Examples
Reference Description
CVE-2004-1056 Product does not properly check if a lock is present, allowing other attackers to
access functionality.
https://www.cve.org/CVERecord?id=CVE-2004-1056
MemberOf Relationships
CWE Version 4.14
CWE-415: Double Free
CWE-415: Double Free