# CVE-2024-37150: Private npm registry support used scope auth token for downloading tarballs

> Deno leaks private npm registry credentials to third-party domains when downloading tarballs, exposing sensitive authentication tokens to attackers.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Jun 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-rfc6-h225-3vxv

## What is CVE-2024-37150?

CVE-2024-37150 is a high-severity vulnerability in denoland deno, published on 6 Jun 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An issue in `.npmrc` support in Deno 1.44.0 was discovered where Deno would send `.npmrc` credentials for the scope to the tarball URL when the registry provided URLs for a tarball on a different domain. All users relying on .npmrc are potentially affected by this vulnerability if their private registry references tarball URLs at a different domain. This includes usage of deno install subcommand, auto-install for npm: specifiers and LSP usage. It is recommended to upgrade to Deno 1.44.1 and if your private registry ever serves tarballs at a different domain to rotate your registry credentials.

Weakness: CWE-706 (Use of Incorrectly-Resolved Name or Reference), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2024-37150?

It affects 1 product.


Products: Deno Deno.

## How do I fix CVE-2024-37150?

No fix has been published for CVE-2024-37150 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-37150 being exploited?

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

## Other vulnerabilities in denoland deno

- [CVE-2023-28445](https://insights.sbomify.com/CVE-2023-28445/): Deno improperly handles resizable ArrayBuffer (critical 10.0)
- [CVE-2022-24783](https://insights.sbomify.com/CVE-2022-24783/): Sandbox bypass leading to arbitrary code execution in Deno (critical 10.0)
- [CVE-2021-32619](https://insights.sbomify.com/CVE-2021-32619/): Static imports inside dynamically imported modules do not adhere to permission checks (critical 9.8)
- [CVE-2026-22863](https://insights.sbomify.com/CVE-2026-22863/): Deno node:crypto doesn't finalize cipher (critical 9.2)
- [CVE-2024-27936](https://insights.sbomify.com/CVE-2024-27936/): Deno interactive permission prompt spoofing via improper ANSI stripping (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-37150 and fix it if it is affected.

What it is: CVE-2024-37150 is a high-severity vulnerability in denoland deno, published on 6 Jun 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-37150 in the wild and no public exploit code.

Affected product: denoland deno. 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-2024-37150/ (Markdown: https://insights.sbomify.com/CVE-2024-37150/index.md)
```

## Sources

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

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