Vulnerability advisory

CVE-2022-31091

Change in port should be considered a change in origin in Guzzle

Published Updated OSV record ↗

Also known as GHSA-q559-8m2m-g699

Severity
  • CVSS 3.xCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Affected versions

Repository

Affected commitsFixed by commit
GIT github.com/guzzle/guzzle ↗
All commits before a52f0440530b54fa079ce76e8c5d196a42cad981a52f0440530b54fa079ce76e8c5d196a42cad981
414c24961042f6616fb43e23fa69a785f9fc053e to before 1dd98b0564cb3f6bd16ce683cb755f94c10fbd821dd98b0564cb3f6bd16ce683cb755f94c10fbd82
Also listed as affected (130)
  • 6.5.7
  • 7.4.4
  • 7.4.3
  • 6.5.6
  • 7.4.2
  • 7.4.1
  • 7.4.0
  • 7.3.0
  • 7.2.0
  • 7.1.1
  • 7.1.0
  • 6.5.5
  • 7.0.0
  • 6.5.4
  • 6.5.3
  • 6.5.2
  • 6.5.1
  • 6.5.0
  • 6.4.1
  • 6.4.0
  • 6.3.3
  • 6.3.2
  • 6.3.1
  • 6.3.0
  • 6.2.2
  • 6.2.1
  • 4.2.3
  • 6.2.0
  • 6.1.1
  • 6.1.0
  • 6.0.2
  • 6.0.1
  • 6.0.0
  • 5.3.0
  • 5.2.0
  • 5.1.0
  • 5.0.3
  • 5.0.2
  • 5.0.1
  • 5.0.0
  • 4.2.2
  • 4.2.1
  • 4.2.0
  • 4.1.8
  • 4.1.7
  • 4.1.6
  • 4.1.5
  • 4.1.4
  • 4.1.3
  • 4.1.2
  • 4.1.1
  • 4.1.0
  • 4.0.2
  • 4.0.1
  • 4.0.0
  • 4.0.0-rc.2
  • 4.0.0-rc.1
  • v3.8.1
  • v3.8.0
  • v3.7.4
  • v3.7.3
  • v3.7.2
  • v3.7.1
  • v3.7.0
  • v3.6.0
  • v3.5.0
  • v3.4.3
  • v3.4.2
  • v3.4.1
  • v3.4.0
  • v3.3.1
  • v3.3.0
  • v3.2.0
  • v3.1.2
  • v3.1.1
  • v3.1.0
  • v3.0.7
  • v3.0.6
  • v3.0.5
  • v3.0.4
  • v3.0.3
  • v3.0.2
  • v3.0.1
  • v3.0.0
  • v2.8.8
  • v2.8.7
  • v2.8.6
  • v2.8.5
  • v2.8.4
  • v2.8.3
  • v2.8.2
  • v2.8.1
  • v2.8.0
  • v2.7.2
  • v2.7.1
  • v2.7.0
  • v2.6.6
  • v2.6.5
  • v2.6.4
  • v2.6.3
  • v2.6.2
  • v2.6.1
  • v2.6.0
  • v2.5.0
  • v2.4.1
  • v2.4.0
  • v2.3.2
  • v2.3.1
  • v2.3.0
  • v2.2.4
  • v2.2.3
  • v2.2.2
  • v2.2.1
  • v2.2.0
  • v2.1.4
  • v2.1.3
  • v2.1.2
  • v2.1.1
  • v2.1.0
  • v2.0.5
  • v2.0.4
  • v2.0.3
  • v2.0.2
  • v2.0.1
  • v2.0.0
  • v1.0.3
  • v1.0.2
  • v1.0.1
  • v1.0.0
  • v1.0.0beta1

Description

Guzzle, an extensible PHP HTTP client. Authorization and Cookie headers on requests are sensitive information. In affected versions on making a request which responds with a redirect to a URI with a different port, if we choose to follow it, we should remove the Authorization and Cookie headers from the request, before containing. Previously, we would only consider a change in host or scheme. 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. An alternative approach would be to use your own redirect middleware, rather than ours, if you are unable to upgrade. If you do not require or expect redirects to be followed, one should simply disable redirects all together.

References

  • Codex
  • Claude Code
  • VS Code
  • GitHub Copilot
  • Cursor
  • Cline
  • Windsurf
  • Google Anti-gravity
  • OpenCode
  • Pi
  • Gemini CLI
  • Hermes Agent
  • Zed
  • Junie
  • Qwen Code
  • Kiro
  • Kilo Code
  • Factory Droid

Set up GitHits for your agents

Run this command:

<> bash
npx githits@latest init

What happens next:

  1. Opens your browser to authorize GitHits
  2. Asks whether to set up GitHits at the user or project level
  3. Detects your supported AI coding tools
  4. Lets you choose which tools to configure
  5. Configures the selected tools