{"answers":{"affected":"2 open source packages ship an affected version, including golang and stdlib.","exploited":"There is no known exploitation of CVE-2023-45289 in the wild and no public exploit code.","fix":"Upgrade golang to a fixed version for your release line: 1.21.8 or 1.22.1.","what":"CVE-2023-45289 is a medium-severity vulnerability in Go standard library net/http, published on 5 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-45289 and fix it if it is affected.\n\nWhat it is: CVE-2023-45289 is a medium-severity vulnerability in Go standard library net/http, published on 5 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-45289 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- golang (Bitnami): affected all versions; fixed in 1.21.8, 1.22.1\n- stdlib (Go): affected all versions; fixed in 1.21.8, 1.22.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-2023-45289/ (Markdown: https://insights.sbomify.com/CVE-2023-45289/index.md)","id":"CVE-2023-45289","markdown":"https://insights.sbomify.com/CVE-2023-45289/index.md","name":"CVE-2023-45289","record":{"aliases":["AZL-37462","AZL-37473","AZL-78974","AZL-98628","BELL-CVE-2023-45289","BIT-golang-2023-45289","DEBIAN-CVE-2023-45289","GHSA-32ch-6x54-q4h9","GO-2024-2600","MINI-2g8g-8v6x-57mv","MINI-3cgq-w4x4-g3w9","MINI-wqf9-jxhm-7x9r","UBUNTU-CVE-2023-45289"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Go standard library","requires_auth":"low_privilege","summary":"A malicious HTTP redirect can cause sensitive headers like Authorization or Cookies to be unexpectedly forwarded to a different domain, leaking credentials.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Go","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[],"description":"When following an HTTP redirect to a domain which is not a subdomain match or exact match of the initial domain, an http.Client does not forward sensitive headers such as \"Authorization\" or \"Cookie\". For example, a redirect from foo.com to www.foo.com will forward the Authorization header, but a redirect to bar.com will not. A maliciously crafted HTTP redirect could cause sensitive headers to be unexpectedly forwarded.","ecosystems":["Bitnami","Go"],"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":"Incorrect forwarding of sensitive headers and cookies on HTTP redirect in net/http","id":"CVE-2023-45289","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":2,"n_references":6,"next":{"headline":"Memory exhaustion in multipart form parsing in net/textproto and net/http","id":"CVE-2023-45290"},"packages":[{"ecosystem":"Bitnami","fixed":["1.21.8","1.22.1"],"introduced":["0","1.22.0-0"],"last_affected":[],"package":"golang","purl":"pkg:bitnami/golang","source":"BIT-golang-2023-45289"},{"ecosystem":"Go","fixed":["1.21.8","1.22.1"],"introduced":["0","1.22.0-0"],"last_affected":[],"package":"stdlib","purl":"pkg:golang/stdlib","source":"GO-2024-2600"}],"prev":{"headline":"HTTP/2 CONTINUATION flood in net/http","id":"CVE-2023-45288"},"products":["net/http","net/http/cookiejar"],"published":"2024-03-05","related":[],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-13","vendors":["Go standard library"]},"summary":"A malicious HTTP redirect can cause sensitive headers like Authorization or Cookies to be unexpectedly forwarded to a different domain, leaking credentials.","url":"https://insights.sbomify.com/CVE-2023-45289/"}