BaseIncomplete

CWE-764Multiple Locks of a Critical Resource

Category: logic

Description

The product locks a critical resource more times than intended, leading to an unexpected state in the system. When a product is operating in a concurrent environment and repeatedly locks a critical resource, the consequences will vary based on the type of lock, the lock's implementation, and the resource being protected. In some situations such as with semaphores, the resources are pooled and extra locking calls will reduce the size of the total available pool, possibly leading to degraded performance or a denial of service. If this can be triggered by an attacker, it will be similar to an unrestricted lock (CWE-412). In the context of a binary lock, it is likely that any duplicate locking attempts will never succeed since the lock is already held and progress may not be possible.

Common consequences· 1

  • Availability / Integrity — DoS: Resource Consumption (CPU), DoS: Crash, Exit, or Restart, Unexpected State

Potential mitigations· 1

  • [Implementation]When locking and unlocking a resource, try to be sure that all control paths through the code in which the resource is locked one or more times correspond to exactly as many unlocks. If the software acquires a lock and then determines it is not able to perform its intended behavior, be sure to release the lock(s) before waiting for conditions to improve. Reacquire the lock(s) before trying again.

References

  1. https://cwe.mitre.org/data/definitions/764.html

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CWE
Multiple Unlocks of a Critical Resource
CWE
Unrestricted Externally Accessible Lock
CWE
Improper Resource Locking
CWE
Missing Lock Check
CWE
Incorrect Synchronization
CWE
Double-Checked Locking
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.