{"answers":{"affected":"2 open source packages ship an affected version, including @actions/http-client. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-11021 in the wild and no public exploit code.","fix":"Upgrade @actions/http-client to 1.0.8 or later.","what":"CVE-2020-11021 is a medium-severity vulnerability in actions http-client, published on 29 Apr 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-11021 and fix it if it is affected.\n\nWhat it is: CVE-2020-11021 is a medium-severity vulnerability in actions http-client, published on 29 Apr 2020. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-11021 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @actions/http-client (npm): affected all versions; fixed in 1.0.8\n- @actions/http-client (npm): affected all versions; fixed in 1.0.8\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-11021/ (Markdown: https://insights.sbomify.com/CVE-2020-11021/index.md)","id":"CVE-2020-11021","markdown":"https://insights.sbomify.com/CVE-2020-11021/index.md","name":"CVE-2020-11021","record":{"aliases":["GHSA-9w6v-m7wp-jwg4"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"GitHub Actions HTTP client","requires_auth":"low_privilege","summary":"Attackers can steal authorization headers when HTTP requests redirect to a different domain, exposing sensitive credentials to unintended hosts.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"http-client","vendor":"http-client_project"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Actions Http-Client (NPM @actions/http-client) before version 1.0.8 can disclose Authorization headers to incorrect domain in certain redirect scenarios. The conditions in which this happens are if consumers of the http-client: 1. make an http request with an authorization header 2. that request leads to a redirect (302) and 3. the redirect url redirects to another domain or hostname Then the authorization header will get passed to the other domain. The problem is fixed in version 1.0.8.","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":"HTTP request which redirect to another hostname do not strip authorization header in Actions Http-Client","id":"CVE-2020-11021","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":2,"n_references":3,"next":{"headline":"jQuery has a potential XSS vulnerability","id":"CVE-2020-11022"},"packages":[{"ecosystem":"npm","fixed":["1.0.8"],"introduced":["0"],"last_affected":[],"package":"@actions/http-client","purl":null,"source":"GHSA-9w6v-m7wp-jwg4"},{"ecosystem":"npm","fixed":["1.0.8"],"introduced":["0"],"last_affected":[],"package":"@actions/http-client","purl":"pkg:npm/%40actions/http-client","source":"GHSA-9w6v-m7wp-jwg4"}],"prev":{"headline":"Authentication and extension bypass in Faye","id":"CVE-2020-11020"},"products":["http-client"],"published":"2020-04-29","related":[],"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":["actions"]},"summary":"Attackers can steal authorization headers when HTTP requests redirect to a different domain, exposing sensitive credentials to unintended hosts.","url":"https://insights.sbomify.com/CVE-2020-11021/"}