{"answers":{"affected":"4 open source packages ship an affected version, including guzzlehttp/guzzle. It affects 2 products.","exploited":"There is no known exploitation of CVE-2022-31090 in the wild and no public exploit code.","fix":"Upgrade guzzlehttp/guzzle to a fixed version for your release line: 6.5.8 or 7.4.5.","what":"CVE-2022-31090 is a high-severity vulnerability in Debian Debian Linux, published on 27 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-31090 and fix it if it is affected.\n\nWhat it is: CVE-2022-31090 is a high-severity vulnerability in Debian Debian Linux, published on 27 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-31090 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- guzzlehttp/guzzle (Packagist): affected all versions; fixed in 6.5.8\n- guzzlehttp/guzzle (Packagist): affected all versions; fixed in 6.5.8\n- guzzlehttp/guzzle (Packagist): affected from 7.0.0; fixed in 7.4.5\n- guzzlehttp/guzzle (Packagist): affected from 7.0.0; fixed in 7.4.5\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-2022-31090/ (Markdown: https://insights.sbomify.com/CVE-2022-31090/index.md)","id":"CVE-2022-31090","markdown":"https://insights.sbomify.com/CVE-2022-31090/index.md","name":"CVE-2022-31090","record":{"aliases":["DEBIAN-CVE-2022-31090","GHSA-25mq-v84q-4j7r","UBUNTU-CVE-2022-31090"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"PHP HTTP client","requires_auth":"low_privilege","summary":"Attackers can steal sensitive Authorization headers when Guzzle follows cross-origin redirects using the Curl handler, exposing credentials to unintended destinations.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"debian_linux","vendor":"debian"},{"product":"guzzle","vendor":"guzzlephp"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-212","name":"Improper Removal of Sensitive Information Before Storage or Transfer"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Guzzle, an extensible PHP HTTP client. `Authorization` headers on requests are sensitive information. In affected versions when using our Curl handler, it is possible to use the `CURLOPT_HTTPAUTH` option to specify an `Authorization` header. On making a request which responds with a redirect to a URI with a different origin (change in host, scheme or port), if we choose to follow it, we should remove the `CURLOPT_HTTPAUTH` option before continuing, stopping curl from appending the `Authorization` header to the new request. Affected Guzzle 7 users should upgrade to Guzzle 7.4.5 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.8 or 7.4.5. Note that a partial fix was implemented in Guzzle 7.4.2, where a change in host would trigger removal of the curl-added Authorization header, however this earlier fix did not cover change in scheme or change in port. If you do not require or expect redirects to be followed, one should simply disable redirects all together. Alternatively, one can specify to use the Guzzle steam handler backend, rather than curl.","ecosystems":["Packagist"],"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":"CURLOPT_HTTPAUTH option not cleared on change of origin in Guzzle","id":"CVE-2022-31090","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":"debian:debian_linux","products":["debian:debian_linux"],"type":"information_disclosure","year":"2022"},"n_packages":4,"n_references":4,"next":{"headline":"Change in port should be considered a change in origin in Guzzle","id":"CVE-2022-31091"},"packages":[{"ecosystem":"Packagist","fixed":["6.5.8"],"introduced":["0"],"last_affected":[],"package":"guzzlehttp/guzzle","purl":null,"source":"GHSA-25mq-v84q-4j7r"},{"ecosystem":"Packagist","fixed":["6.5.8"],"introduced":["0"],"last_affected":[],"package":"guzzlehttp/guzzle","purl":"pkg:composer/guzzlehttp/guzzle","source":"GHSA-25mq-v84q-4j7r"},{"ecosystem":"Packagist","fixed":["7.4.5"],"introduced":["7.0.0"],"last_affected":[],"package":"guzzlehttp/guzzle","purl":null,"source":"GHSA-25mq-v84q-4j7r"},{"ecosystem":"Packagist","fixed":["7.4.5"],"introduced":["7.0.0"],"last_affected":[],"package":"guzzlehttp/guzzle","purl":"pkg:composer/guzzlehttp/guzzle","source":"GHSA-25mq-v84q-4j7r"}],"prev":{"headline":"Invalid file request can crashe parse-server","id":"CVE-2022-31089"},"products":["guzzle"],"published":"2022-06-27","related":[{"cvss_score":10,"headline":"ProFTPD Improper Access Control","id":"CVE-2015-3306","kev_date_added":"2026-10-08","published":"2015-05-18"},{"cvss_score":9.9,"headline":"RoundCube Webmail Deserialization of Untrusted Data","id":"CVE-2025-49113","kev_date_added":"2026-02-20","published":"2025-06-02"},{"cvss_score":9.8,"headline":"GNU InetUtils Argument Injection","id":"CVE-2026-24061","kev_date_added":"2026-01-26","published":"2026-01-21"},{"cvss_score":9.8,"headline":"Linux Kernel Improper Check for Unusual or Exceptional Conditions","id":"CVE-2025-39682","kev_date_added":"2026-09-18","published":"2025-09-05"},{"cvss_score":9.8,"headline":"Mozilla Firefox Use-After-Free","id":"CVE-2024-9680","kev_date_added":"2024-10-15","published":"2024-10-09"},{"cvss_score":9.8,"headline":"RARLAB UnRAR Directory Traversal","id":"CVE-2022-30333","kev_date_added":"2022-08-09","published":"2022-05-09"},{"cvss_score":9.8,"headline":"Roundcube Webmail SQL Injection","id":"CVE-2021-44026","kev_date_added":"2023-06-22","published":"2021-11-19"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["guzzle"]},"summary":"Attackers can steal sensitive Authorization headers when Guzzle follows cross-origin redirects using the Curl handler, exposing credentials to unintended destinations.","url":"https://insights.sbomify.com/CVE-2022-31090/"}