We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.
Please see our statement on Data Privacy.
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.
Reserved 2024-06-03 | Published 2024-06-06 | Updated 2024-08-02 | Assigner GitHub_MCWE-200: Exposure of Sensitive Information to an Unauthorized Actor
github.com/...d/deno/security/advisories/GHSA-rfc6-h225-3vxv
github.com/...ommit/566adb7c0a0c0845e90a6e867a2c0ef5d2ada575
github.com/...for-URI,-but-auth-present-for-scoped-registry"
Support options