CyberRota Analysis
AI-GeneratedVersions of guzzlehttp/guzzle prior to 7.15.1 are vulnerable to an information disclosure issue in RedirectMiddleware, specifically when the optional allow_redirects.referer setting is enabled. This flaw allows an attacker controlling the redirect destination to access sensitive data, such as one-time login secrets and access tokens, through the Referer header. Organizations using affected versions should prioritize upgrading to 7.15.1 to mitigate potential data leaks.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
guzzlehttp/guzzle versions before 7.15.1 contain an information disclosure vulnerability in RedirectMiddleware. When the optional allow_redirects.referer setting is enabled, the middleware copies the URI fragment (the portion after '#') from the referring request into the generated Referer header when following a same-scheme redirect (e.g., HTTPS to HTTPS). An attacker who controls the redirect destination can read this fragment from the incoming Referer header, potentially disclosing one-time login secrets, access tokens, state values, or other sensitive client data to a server never meant to receive it. The referer setting is disabled by default. Fixed in 7.15.1, which strips the fragment before generating the Referer value.