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.
CVSS 3.x
| Source | Score | Severity | Vector | Exploitability | Impact |
|---|---|---|---|---|---|
| security-advisories@github.com | 2.6 | LOW | CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L | 1.2 | 1.4 |
| nvd@nist.gov | 5.3 | MEDIUM | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | 3.9 | 1.4 |
CVSS 2.0
Severity: MEDIUM
Problem Type: CWE-20,CWE-770,CWE-770,
Products Affected
| Vendor | Product | Version |
|---|---|---|
| node-fetch_project | node-fetch | * |
| node-fetch_project | node-fetch | 3.0.0 |
node-fetch is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor
CVSS 2.0
Severity: MEDIUM
Problem Type: CWE-200,CWE-601,
Products Affected
| Vendor | Product | Version |
|---|---|---|
| siemens | sinec_ins | * |
| siemens | sinec_ins | 1.0 |
| debian | debian_linux | 10.0 |
| node-fetch_project | node-fetch | * |
Inefficient Regular Expression Complexity in GitHub repository node-fetch/node-fetch prior to 3.2.10.
CVSS 3.x
| Source | Score | Severity | Vector | Exploitability | Impact |
|---|---|---|---|---|---|
| nvd@nist.gov | 5.9 | MEDIUM | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H | 2.2 | 3.6 |
Products Affected
| Vendor | Product | Version |
|---|---|---|
| node-fetch_project | node-fetch | * |