CWE-667Improper Locking

Description

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

Common consequences

• Availability→DoS: Resource Consumption (CPU)
  Inconsistent locking discipline can lead to deadlock.
• Integrity→Modify Memory,Modify Application Data
  This can lead to data or memory corruption.
• Other→Varies by Context,Unexpected State
  This can lead to unexpected resource state changes and behaviors.

Potential mitigations

• Implementation
  Use industry standard APIs to implement locking mechanism.

Related CWEs

Recent CVEs classified under this CWE