npm package
send 0.17.1 vulnerability, and the version that fixes it
send 0.17.1 has 1 known vulnerability; 0.19.0 fixes it.
npm (opens in a new tab) describes it as “Better streaming static file server with Range and conditional-GET support”
- Known vulnerabilities
- 1
- None rated high or critical
- Released
- May 11, 2019
- Latest is 1.2.1
- Downloads last week
- 2.5M
- 2% of send downloads
- Licence
- MIT
- Pulls in
- 18 packages
- Resolved by deps.dev
What to upgrade to
0.19.0 is the closest release with no known vulnerabilities.
Findings
- LowVulnerability
CVE-2024-43799 in send 0.17.1
EPSS: top 56%send vulnerable to template injection that can lead to XSS. Fixed in 0.19.0.
- LowOutdated
send 0.17.1 is 1 major version behind
Latest release is 1.2.1.
Every advisory for send 0.17.1
Known exploited first (CISA KEV), then by how likely they are to be exploited (FIRST EPSS), then by severity. Each id links to its OSV.dev record.
LowCVE-2024-43799 on OSV.dev (opens in a new tab)GHSA-m6fv-jmcg-4jfgEPSS: top 56%
send vulnerable to template injection that can lead to XSS
Fixed in 0.19.0. Published Sep 10, 2024.
Who is still on a vulnerable send
7% of last week’s 153.5M send downloads went to versions with known vulnerabilities.
From npm’s per-version download counts for the last 7 days, each version checked against OSV.dev. The versions checked cover over 99% of downloads.
Is send the only one?
Paste a public GitHub repo or drop your package.json and see every vulnerable, end-of-life or deprecated dependency, with one fix task. Free, no sign-up.
How this page is checked
StackPrism asks OSV.dev which advisories affect exactly send 0.17.1, merges duplicates filed under several ids, and ranks them with CISA’s Known Exploited Vulnerabilities list and FIRST EPSS. Release dates and deprecation come from deps.dev and npm. No AI writes this page: every sentence comes from that data, refreshed every few hours.
Last checked against npm, OSV.dev, deps.dev, CISA KEV and FIRST EPSS.