CWE

Common Weakness Enumeration

A Community-Developed Dictionary of Software Weakness Types

CWE/SANS Top 25 Most Dangerous Software Errors Common Weakness Scoring System
Common Weakness Risk Analysis Framework
Home > CWE List > CWE- Individual Dictionary Definition (2.7)  

Presentation Filter:

CWE-662: Improper Synchronization

 
Improper Synchronization
Weakness ID: 662 (Weakness Base)Status: Draft
+ Description

Description Summary

The software attempts to use a shared resource in an exclusive manner, but does not prevent or incorrectly prevents use of the resource by another thread or process.
+ Time of Introduction
  • Architecture and Design
  • Implementation
+ Common Consequences
ScopeEffect

Technical Impact: Modify application data; Read application data; Alter execution logic

+ Potential Mitigations

Phase: Implementation

Use industry standard APIs to synchronize your code.

+ Relationships
NatureTypeIDNameView(s) this relationship pertains toView(s)
ChildOfCategoryCategory361Time and State
Development Concepts (primary)699
ChildOfWeakness ClassWeakness Class664Improper Control of a Resource Through its Lifetime
Research Concepts (primary)1000
ChildOfWeakness ClassWeakness Class691Insufficient Control Flow Management
Research Concepts1000
ChildOfCategoryCategory745CERT C Secure Coding Section 11 - Signals (SIG)
Weaknesses Addressed by the CERT C Secure Coding Standard (primary)734
ChildOfCategoryCategory852CERT Java Secure Coding Section 07 - Visibility and Atomicity (VNA)
Weaknesses Addressed by the CERT Java Secure Coding Standard (primary)844
ChildOfCategoryCategory879CERT C++ Secure Coding Section 11 - Signals (SIG)
Weaknesses Addressed by the CERT C++ Secure Coding Standard (primary)868
ChildOfCategoryCategory894SFP Cluster: Synchronization
Software Fault Pattern (SFP) Clusters (primary)888
CanPrecedeWeakness ClassWeakness Class362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Development Concepts699
Research Concepts1000
ParentOfWeakness BaseWeakness Base663Use of a Non-reentrant Function in a Concurrent Context
Research Concepts (primary)1000
ParentOfWeakness BaseWeakness Base667Improper Locking
Development Concepts (primary)699
Research Concepts (primary)1000
ParentOfWeakness BaseWeakness Base820Missing Synchronization
Development Concepts (primary)699
Research Concepts (primary)1000
ParentOfWeakness BaseWeakness Base821Incorrect Synchronization
Development Concepts (primary)699
Research Concepts (primary)1000
+ Taxonomy Mappings
Mapped Taxonomy NameNode IDFitMapped Node Name
CERT C Secure CodingSIG00-CMask signals handled by noninterruptible signal handlers
CERT C Secure CodingSIG31-CDo not access or modify shared objects in signal handlers
CLASPState synchronization error
CERT Java Secure CodingVNA03-JDo not assume that a group of calls to independently atomic methods is atomic
CERT C++ Secure CodingSIG00-CPPMask signals handled by noninterruptible signal handlers
CERT C++ Secure CodingSIG31-CPPDo not access or modify shared objects in signal handlers
+ Content History
Modifications
Modification DateModifierOrganizationSource
2008-07-01CigitalExternal
updated Potential_Mitigations, Time_of_Introduction
2008-09-08MITREInternal
updated Relationships
2008-10-14MITREInternal
updated Relationships
2008-11-24MITREInternal
updated Relationships, Taxonomy_Mappings
2009-03-10MITREInternal
updated Related_Attack_Patterns
2009-05-27MITREInternal
updated Relationships
2010-09-27MITREInternal
updated Name, Relationships
2010-12-13MITREInternal
updated Description, Relationships, Taxonomy_Mappings
2011-06-01MITREInternal
updated Common_Consequences, Relationships, Taxonomy_Mappings
2011-09-13MITREInternal
updated Relationships, Taxonomy_Mappings
2012-05-11MITREInternal
updated Relationships
2012-10-30MITREInternal
updated Potential_Mitigations
2013-07-17MITREInternal
updated Relationships
Previous Entry Names
Change DatePrevious Entry Name
2010-09-27Insufficient Synchronization
Page Last Updated: June 23, 2014