Deno 1.44.0
Approved changes feed: RSS · Atom
cpe:2.3:a:deno:deno:1.44.0:*:*:*:*:*:*:*
part: a version: 1.44.0 update: *
| Vendor | Deno (d5afa7ad-1b4a-5b28-9776-7b90d94bc7bf) |
|---|---|
| Product | Deno (a875d440-11d8-546a-be1d-34922ca0bde4) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/denoland/deno |
purl2cpe | 2026-06-01 10:12:51.739783 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-37150 |
vulnerable | 2026-06-08 06:39:46.714434 |
Private npm registry support used scope auth token for downloading tarballs
HIGH (7.6)
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.
Published: 2024-06-06T15:28:14.216Z
Updated: 2024-08-02T03:50:54.672Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.