{"answers":{"affected":"4 open source packages ship an affected version, including node-fetch. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-15168 in the wild and no public exploit code.","fix":"Upgrade node-fetch to a fixed version for your release line: 2.6.1 or 3.0.0-beta.9.","what":"CVE-2020-15168 is a low-severity denial of service vulnerability in node-fetch, published on 10 Sep 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-15168 and fix it if it is affected.\n\nWhat it is: CVE-2020-15168 is a low-severity denial of service vulnerability in node-fetch, published on 10 Sep 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-15168 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- node-fetch (npm): affected from 2.0.0; fixed in 2.6.1\n- node-fetch (npm): affected from 2.0.0; fixed in 2.6.1\n- node-fetch (npm): affected from 3.0.0-beta.1; fixed in 3.0.0-beta.9\n- node-fetch (npm): affected from 3.0.0-beta.1; fixed in 3.0.0-beta.9\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2020-15168/ (Markdown: https://insights.sbomify.com/CVE-2020-15168/index.md)","id":"CVE-2020-15168","markdown":"https://insights.sbomify.com/CVE-2020-15168/index.md","name":"CVE-2020-15168","record":{"aliases":["DEBIAN-CVE-2020-15168","GHSA-w7rc-rwvf-8q5r","UBUNTU-CVE-2020-15168"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Node.js HTTP client","requires_auth":"low_privilege","summary":"Attackers can bypass file size limits in node-fetch redirects, causing resource exhaustion and denial of service in applications relying on this check.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"node-fetch","vendor":"node-fetch_project"}],"cvss":{"score":2.6,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"File size limit bypass in node-fetch","id":"CVE-2020-15168","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2020"},"n_packages":4,"n_references":2,"next":{"headline":"XSS in Action View","id":"CVE-2020-15169"},"packages":[{"ecosystem":"npm","fixed":["2.6.1"],"introduced":["2.0.0"],"last_affected":[],"package":"node-fetch","purl":null,"source":"GHSA-w7rc-rwvf-8q5r"},{"ecosystem":"npm","fixed":["2.6.1"],"introduced":["2.0.0"],"last_affected":[],"package":"node-fetch","purl":"pkg:npm/node-fetch","source":"GHSA-w7rc-rwvf-8q5r"},{"ecosystem":"npm","fixed":["3.0.0-beta.9"],"introduced":["3.0.0-beta.1"],"last_affected":[],"package":"node-fetch","purl":null,"source":"GHSA-w7rc-rwvf-8q5r"},{"ecosystem":"npm","fixed":["3.0.0-beta.9"],"introduced":["3.0.0-beta.1"],"last_affected":[],"package":"node-fetch","purl":"pkg:npm/node-fetch","source":"GHSA-w7rc-rwvf-8q5r"}],"prev":{"headline":"Arbitrary code execution via configuration file in Miller","id":"CVE-2020-15167"},"products":["node-fetch"],"published":"2020-09-10","related":[{"cvss_score":5.9,"headline":"Inefficient Regular Expression Complexity in node-fetch/node-fetch","id":"CVE-2022-2596","kev_date_added":null,"published":"2022-08-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["node-fetch"]},"summary":"Attackers can bypass file size limits in node-fetch redirects, causing resource exhaustion and denial of service in applications relying on this check.","url":"https://insights.sbomify.com/CVE-2020-15168/"}