Vulnerabilities · 2024 · Deno
CVE-2024-37150
Deno vulnerability
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.
Affected products
Deno. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Deno runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/denoland/deno/security/advisories/GHSA-rfc6-h225-3vxv · Vendor Advisory
- github.com/denoland/deno/commit/566adb7c0a0c0845e90a6e867a2c0ef5d2ada575 · Patch
- github.com/npm/cli/wiki/%22No-auth-for-URI,-but-auth-present-for-scoped-registry%22
- nvd.nist.gov/vuln/detail/CVE-2024-37150
- cve.org/CVERecord?id=CVE-2024-37150
More vulnerabilities in Deno products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.