Node Fetch
Approved changes feed: RSS · Atom
cpe:2.3:a:node-fetch:node-fetch:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Node Fetch (68ac2a24-7860-543f-bbce-f3373a2d8f41) |
|---|---|
| Product | Node Fetch (f39f747d-4077-5bf1-8f61-8343bd4dce89) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2020-15168 |
vulnerable | 2026-06-08 05:19:25.412997 |
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 |
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.