{"answers":{"affected":"2 open source packages ship an affected version, including axios. It affects 2 products.","exploited":"There is no known exploitation of CVE-2020-28168 in the wild and no public exploit code.","fix":"Upgrade axios to 0.21.1 or later.","what":"CVE-2020-28168 is a medium-severity server-side request forgery vulnerability in n/a, published on 6 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-28168 and fix it if it is affected.\n\nWhat it is: CVE-2020-28168 is a medium-severity server-side request forgery vulnerability in n/a, published on 6 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-28168 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- axios (npm): affected all versions; fixed in 0.21.1\n- axios (npm): affected all versions; fixed in 0.21.1\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-28168/ (Markdown: https://insights.sbomify.com/CVE-2020-28168/index.md)","id":"CVE-2020-28168","markdown":"https://insights.sbomify.com/CVE-2020-28168/index.md","name":"CVE-2020-28168","record":{"aliases":["DEBIAN-CVE-2020-28168","GHSA-4w2v-q235-vp99","ROOT-APP-NPM-CVE-2020-28168","UBUNTU-CVE-2020-28168"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Axios HTTP client","requires_auth":"none","summary":"An attacker can bypass proxy restrictions to access internal hosts via redirect in the Axios HTTP client library.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"axios","vendor":"axios"},{"product":"sinec_ins","vendor":"siemens"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Axios NPM package 0.21.0 contains a Server-Side Request Forgery (SSRF) vulnerability where an attacker is able to bypass a proxy by providing a URL that responds with a redirect to a restricted host or IP address.","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":"Axios vulnerable to Server-Side Request Forgery","id":"CVE-2020-28168","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"ssrf","year":"2020"},"n_packages":2,"n_references":5,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2020-28169"},"packages":[{"ecosystem":"npm","fixed":["0.21.1"],"introduced":["0"],"last_affected":[],"package":"axios","purl":null,"source":"GHSA-4w2v-q235-vp99"},{"ecosystem":"npm","fixed":["0.21.1"],"introduced":["0"],"last_affected":[],"package":"axios","purl":"pkg:npm/axios","source":"GHSA-4w2v-q235-vp99"}],"prev":{"headline":"File upload in n/a","id":"CVE-2020-28165"},"products":["n/a"],"published":"2020-11-06","related":[{"cvss_score":8.7,"headline":"Axios: Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`","id":"CVE-2026-44494","kev_date_added":null,"published":"2026-06-11"},{"cvss_score":8.6,"headline":"axios's shouldBypassProxy does not recognize IPv4-mapped IPv6 addresses, allowing NO_PROXY bypass (incomplete fix for CVE-2025-62718)","id":"CVE-2026-44492","kev_date_added":null,"published":"2026-06-11"},{"cvss_score":8.3,"headline":"axios before 0.33.0 Prototype Pollution via Node HTTP adapter","id":"CVE-2026-67320","kev_date_added":null,"published":"2026-08-01"},{"cvss_score":8.2,"headline":"Axios: Proxy-Authorization Credential Leak to Origin Server Across HTTP-to-HTTPS Redirect in Axios Node.js HTTP Adapter","id":"CVE-2026-44487","kev_date_added":null,"published":"2026-06-11"},{"cvss_score":7.7,"headline":"Possible SSRF and Credential Leakage via Absolute URL in axios Requests","id":"CVE-2025-27152","kev_date_added":null,"published":"2025-03-07"},{"cvss_score":7.5,"headline":"Axios: Proxy-Authorization header leaks to redirect target when proxy is re-evaluated to direct connection","id":"CVE-2026-44486","kev_date_added":null,"published":"2026-06-11"},{"cvss_score":7.5,"headline":"Axios: Allocation of Resources Without Limits or Throttling in axios","id":"CVE-2026-44488","kev_date_added":null,"published":"2026-06-11"}],"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":["n/a"]},"summary":"An attacker can bypass proxy restrictions to access internal hosts via redirect in the Axios HTTP client library.","url":"https://insights.sbomify.com/CVE-2020-28168/"}