Vulnerability in node-fetch (CVE-2020-15168)
Summary
Vulnerability in node-fetch (CVE-2020-15168). Risk of unauthorized operations or information disclosure. Exploitable via size. Mitigation: upgrade to 3.0.0-beta.9 or later.
Original description
The description as published by the source.
Impact
Node Fetch 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.
Patches
We released patched versions for both stable and beta channels:
- For
v2: 2.6.1 - For
v3: 3.0.0-beta.9
Workarounds
None, it is strongly recommended to update as soon as possible.
For more information
If you have any questions or comments about this advisory:
- Open an issue in node-fetch
- Contact one of the core maintainers.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2020-15168 has been found in node-fetch.
Attackers can target a specific entry point like size over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade node-fetch to 3.0.0-beta.9 or later.
If unsure, ask your IT team or search "node-fetch CVE-2020-15168" on the vendor's site.
CVE-2020-15168 (node-fetch) — CWE-20
Attack vector: remote (network-reachable)
Attack surface: size / FetchError
Patched: 3.0.0-beta.9 — apply immediately
Workaround: None, it is strongly recommended to update as soon as possible.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in node-fetch. Attackers reach the vulnerable code path via size.
Check the vendor advisory for the affected versions of node-fetch. Attack surface: size / FetchError.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 3.0.0-beta.9.
Workaround: None, it is strongly recommended to update as soon as possible.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'node-fetch' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'node-fetch' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
node-fetchを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
None, it is strongly recommended to update as soon as possible.パッチが適用されるまでの応急処置として、None, it is strongly recommended to update as soon as possible. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade node-fetch to 3.0.0-beta.9ステージング環境で 3.0.0-beta.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2020-15168 node-fetch Fixed in: 2.6.1-2
References
- advisory npmjs.com
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com