Application deadlock via cross-thread mutex release
Published Feb 11, 2020 · Updated Aug 6, 2024
Race condition in libuv before 1.7.4 allows remote attackers to deadlock applications using the Windows XP or Server 2003 rwlock fallback. The uv_rwlock_t fallback can let one thread release a write mutex acquired by another, violating Windows critical-section ownership. Reachability requires a multithreaded application to exercise that legacy fallback during a race; the bounded outcome is an application hang.
Summary
What happened
Race condition in libuv before 1.7.4 allows remote attackers to deadlock applications using the Windows XP or Server 2003 rwlock fallback. The uv_rwlock_t fallback can let one thread release a write mutex acquired by another, violating Windows critical-section ownership. Reachability requires a multithreaded application to exercise that legacy fallback during a race; the bounded outcome is an application hang.
The record
- CVE
- CVE-2014-9748
- Published
- Feb 11, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-362, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 11, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo