# CVE-2014-9748: Race condition in n/a

> Attackers can cause a denial of service via deadlock in libuv's Windows XP/2003 lock implementation due to a race condition.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Feb 2020
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-9748, GHSA-6w8h-9vfj-7934

## What is CVE-2014-9748?

CVE-2014-9748 is a high-severity vulnerability in Nodejs Node.js, published on 11 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The uv_rwlock_t fallback implementation for Windows XP and Server 2003 in libuv before 1.7.4 does not properly prevent threads from releasing the locks of other threads, which allows attackers to cause a denial of service (deadlock) or possibly have unspecified other impact by leveraging a race condition.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2014-9748?

It affects 2 products.


Products: Libuv Libuv, Nodejs Node.js.

## How do I fix CVE-2014-9748?

Upgrade to a fixed version.

## Is CVE-2014-9748 being exploited?

There is no known exploitation of CVE-2014-9748 in the wild and no public exploit code.

## Other vulnerabilities in Nodejs Node.js

- [CVE-2024-24806](https://insights.sbomify.com/CVE-2024-24806/): Improper Domain Lookup that potentially leads to SSRF attacks in libuv (high 7.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-9748 and fix it if it is affected.

What it is: CVE-2014-9748 is a high-severity vulnerability in Nodejs Node.js, published on 11 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-9748 in the wild and no public exploit code.

Affected product: Nodejs Node.js. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-9748/ (Markdown: https://insights.sbomify.com/CVE-2014-9748/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-9748
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-9748
- OSV: https://osv.dev/vulnerability/CVE-2014-9748

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-9748/
Summaries are generated and may contain mistakes; the official description above is the record.