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.
Metrics
CVSS 3.1 6.5/10
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:NWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| denoland | deno | = 1.44.0 |
References
- https://github.com/denoland/deno/commit/566adb7c0a0c0845e90a6e867a2c0ef5d2ada575Patch
- https://github.com/denoland/deno/security/advisories/GHSA-rfc6-h225-3vxvVendor Advisory
- https://github.com/npm/cli/wiki/%22No-auth-for-URI,-but-auth-present-for-scoped-registry%22Not Applicable
- https://github.com/denoland/deno/commit/566adb7c0a0c0845e90a6e867a2c0ef5d2ada575Patch
- https://github.com/denoland/deno/security/advisories/GHSA-rfc6-h225-3vxvVendor Advisory
- https://github.com/npm/cli/wiki/%22No-auth-for-URI,-but-auth-present-for-scoped-registry%22Not Applicable
Timeline
- Published
- Jun 6, 2024
- Last modified
- Jun 17, 2026
- NVD status
- Modified