GHSA-gv7w-rqvm-qjhr json
Missing binary integrity verification in esbuild Deno module enables remote code execution via NPM_CONFIG_REGISTRY
published 5mo ago modified 2mo ago
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository evanw/esbuild. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 8.1
- version 3.1, the maintainers
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
Security advisory published by the maintainers of evanw/esbuild: the maintainers' own advisory, not a reviewed GitHub Advisory Database entry. The full advisory is on GitHub.
Is GHSA-gv7w-rqvm-qjhr in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| the maintainers | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Classification
References
Sources
- GitHub Advisory GHSA-gv7w-rqvm-qjhr
- Maintainer advisory GHSA-gv7w-rqvm-qjhr
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of evanw/esbuild published their own advisory on GitHub. Reviewed sources take precedence over it.