Unrestricted Externally Accessible Lock
CWE-412
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.
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.
We track 2 vulnerabilities of this type. 100% are rated high or critical, and the average CVSS score is 8.2.
How this weakness is prevented
- Architecture and Design Implementation: Use any access control that is offered by the functionality that is offering the lock.
- Architecture and Design Implementation: Use unpredictable names or identifiers for the locks. This might not always be possible or feasible.
- Architecture and Design: Consider modifying your code to use non-blocking synchronization methods.
Latest Unrestricted Externally Accessible Lock vulnerabilities
- 8.8 High severity
Xen: Unrestricted Externally Accessible Lock
[This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] To manage the system, sysctl and platform operations are used by the control domain or a possible Xenstore domain. Some of these op
- 7.5 High severity
DietPi-Dashboard: Improper Locking
DietPi-Dashboard is a web dashboard for the operating system DietPi. The dashboard only allows for one TLS handshake to be in process at a given moment. Once a TCP connection is established in HTTPS mode, it will assume that it should be waiting for a handshak