CWE-412

Unrestricted Externally Accessible Lock
AI Translation Available

The product properly checks for the existence of a lock, but the lock can be externally controlled or influenced by an actor that is outside of the intended sphere of control.

Status
incomplete
Abstraction
base

This prevents the product from acting on associated resources or performing other behaviors that are controlled by the presence of the lock. Relevant locks might include an exclusive lock or mutex, or modifying a shared resource that is treated as a lock. If the lock can be held for an indefinite period of time, then the denial of service could be permanent.

Common Consequences

availability
Impacts
dos: resource consumption (other)

Detection Methods

white box

Potential Mitigations

Phases:
architecture and design implementation
Descriptions:
• Use any access control that is offered by the functionality that is offering the lock.
• Consider modifying your code to use non-blocking synchronization methods.
• Use unpredictable names or identifiers for the locks. This might not always be possible or feasible.