Improper SynchronizationID: 662 | Date: (C)2012-05-14 (M)2022-10-10 |
Type: weakness | Status: DRAFT |
Abstraction Type: Base |
Description
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.
Applicable PlatformsNone
Time Of Introduction
- Architecture and Design
- Implementation
Related Attack Patterns
Common Consequences
Scope | Technical Impact | Notes |
---|
IntegrityConfidentialityOther | Modify application
dataRead application
dataAlter execution
logic | |
Detection MethodsNone
Potential Mitigations
Phase | Strategy | Description | Effectiveness | Notes |
---|
Implementation | | Use industry standard APIs to synchronize your code. | | |
Relationships
Related CWE | Type | View | Chain |
---|
CWE-662 ChildOf CWE-894 | Category | CWE-888 | |
Demonstrative ExamplesNone
White Box Definitions None
Black Box Definitions None
Taxynomy Mappings
Taxynomy | Id | Name | Fit |
---|
CERT C Secure Coding | SIG00-C | Mask signals handled by noninterruptible signal
handlers | |
CERT C Secure Coding | SIG31-C | Do not access or modify shared objects in signal
handlers | |
CLASP | | State synchronization error | |
CERT Java Secure Coding | VNA03-J | Do not assume that a group of calls to independently atomic
methods is atomic | |
CERT C++ Secure Coding | SIG00-CPP | Mask signals handled by noninterruptible signal
handlers | |
CERT C++ Secure Coding | SIG31-CPP | Do not access or modify shared objects in signal
handlers | |
References:None