Approved changes feed: RSS · Atom

cpe:2.3:a:node-fetch_project:node-fetch:3.0.0:beta1:*:*:*:node.js:*:*

part: a version: 3.0.0 update: beta1

VendorNode Fetch Project (d9b9b723-0d05-53c4-a407-1852bb099ed9)
ProductNode Fetch (49a6b381-8dd4-501a-80c5-ff9fde5c3e33)
Edition*
Language*
Software edition*
Target softwarenode.js
Target hardware*
Other*

Notes

Imported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
pkg:bitbucket/deoates/node-fetch purl2cpe 2026-06-01 10:11:41.528956
pkg:deb/debian/node-fetch purl2cpe 2026-06-01 10:11:41.528958
pkg:deb/ubuntu/node-fetch purl2cpe 2026-06-01 10:11:41.528959
pkg:github/node-fetch/node-fetch purl2cpe 2026-06-01 10:11:41.528960
pkg:maven/org.webjars.npm/node-fetch purl2cpe 2026-06-01 10:11:41.528962
pkg:npm/node-fetch purl2cpe 2026-06-01 10:11:41.528963

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2020-15168 vulnerable 2026-06-08 05:19:25.414618 File size limit bypass in node-fetch
LOW (2.6)
node-fetch before versions 2.6.1 and 3.0.0-beta.9 did not honor the size option after following a redirect, which means that when a content size was over the limit, a FetchError would never get thrown and the process would end without failure. For most people, this fix will have a little or no impact. However, if you are relying on node-fetch to gate files above a size, the impact could be significant, for example: If you don't double-check the size of the data after fetch() has completed, your JS thread could get tied up doing work on a large file (DoS) and/or cost you money in computing.
Published: 2020-09-10T18:25:13.000Z
Updated: 2024-08-04T13:08:22.463Z
Reference links
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.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.