Cookie headers on requests are sensitive information. On making a request using the https scheme to a server which responds with a redirect to a URI with the http scheme, or on making a request to a server which responds with a redirect to a a URI to a different host, we should not forward the Cookie header on. Prior to this fix, only cookies that were managed by our cookie middleware would be safely removed, and any Cookie header manually added to the initial request would not be stripped. We now always strip it, and allow the cookie middleware to re-add any cookies that it deems should be there.
Patches
Affected Guzzle 7 users should upgrade to Guzzle 7.4.4 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.7 or 7.4.4.
Workarounds
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.
If you have any questions or comments about this advisory, please get in touch with us in #guzzle on the PHP HTTP Slack. Do not report additional security advisories in that public channel, however - please follow our vulnerability reporting process.
Authorization headers on requests are sensitive information. On making a request using the https scheme to a server which responds with a redirect to a URI with the http scheme, we should not forward the Authorization header on. This is much the same as to how we don't forward on the header if the host changes. Prior to this fix, https to http downgrades did not result in the Authorization header being removed, only changes to the host.
Patches
Affected Guzzle 7 users should upgrade to Guzzle 7.4.4 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.7 or 7.4.4.
Workarounds
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.
If you have any questions or comments about this advisory, please get in touch with us in #guzzle on the PHP HTTP Slack. Do not report additional security advisories in that public channel, however - please follow our vulnerability reporting process.
Authorization headers on requests are sensitive information. 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, if we choose to follow it, we should remove the CURLOPT_HTTPAUTH and CURLOPT_USERPWD options before continuing, stopping curl from appending the Authorization header to the new request. Previously, we would only consider a change in host. Now, we consider any change in host, port or scheme to be a change in origin.
Patches
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.
Workarounds
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 stream handler backend, rather than curl.
If you have any questions or comments about this advisory, please get in touch with us in #guzzle on the PHP HTTP Slack. Do not report additional security advisories in that public channel, however - please follow our vulnerability reporting process.
Authorization and Cookie headers on requests are sensitive information. 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 downgrade. Now, we consider any change in host, port or scheme to be a change in origin.
Patches
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.
Workarounds
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.
If you have any questions or comments about this advisory, please get in touch with us in #guzzle on the PHP HTTP Slack. Do not report additional security advisories in that public channel, however please follow our vulnerability reporting process.
Release Notes
guzzle/guzzle
### [`v7.4.5`](https://togithub.com/guzzle/guzzle/blob/HEAD/CHANGELOG.md#745---2022-06-20)
[Compare Source](https://togithub.com/guzzle/guzzle/compare/7.4.4...7.4.5)
##### Fixed
- Fix change in port should be considered a change in origin
- Fix `CURLOPT_HTTPAUTH` option not cleared on change of origin
### [`v7.4.4`](https://togithub.com/guzzle/guzzle/blob/HEAD/CHANGELOG.md#744---2022-06-09)
[Compare Source](https://togithub.com/guzzle/guzzle/compare/7.4.3...7.4.4)
##### Fixed
- Fix failure to strip Authorization header on HTTP downgrade
- Fix failure to strip the Cookie header on change in host or HTTP downgrade
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
7.4.3->7.4.5GitHub Vulnerability Alerts
CVE-2022-31042
Impact
Cookieheaders on requests are sensitive information. On making a request using thehttpsscheme to a server which responds with a redirect to a URI with thehttpscheme, or on making a request to a server which responds with a redirect to a a URI to a different host, we should not forward theCookieheader on. Prior to this fix, only cookies that were managed by our cookie middleware would be safely removed, and anyCookieheader manually added to the initial request would not be stripped. We now always strip it, and allow the cookie middleware to re-add any cookies that it deems should be there.Patches
Affected Guzzle 7 users should upgrade to Guzzle 7.4.4 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.7 or 7.4.4.
Workarounds
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
For more information
If you have any questions or comments about this advisory, please get in touch with us in
#guzzleon the PHP HTTP Slack. Do not report additional security advisories in that public channel, however - please follow our vulnerability reporting process.CVE-2022-31043
Impact
Authorizationheaders on requests are sensitive information. On making a request using thehttpsscheme to a server which responds with a redirect to a URI with thehttpscheme, we should not forward theAuthorizationheader on. This is much the same as to how we don't forward on the header if the host changes. Prior to this fix,httpstohttpdowngrades did not result in theAuthorizationheader being removed, only changes to the host.Patches
Affected Guzzle 7 users should upgrade to Guzzle 7.4.4 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.7 or 7.4.4.
Workarounds
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
For more information
If you have any questions or comments about this advisory, please get in touch with us in
#guzzleon the PHP HTTP Slack. Do not report additional security advisories in that public channel, however - please follow our vulnerability reporting process.CVE-2022-31090
Impact
Authorizationheaders on requests are sensitive information. When using our Curl handler, it is possible to use theCURLOPT_HTTPAUTHoption to specify anAuthorizationheader. On making a request which responds with a redirect to a URI with a different origin, if we choose to follow it, we should remove theCURLOPT_HTTPAUTHandCURLOPT_USERPWDoptions before continuing, stopping curl from appending theAuthorizationheader to the new request. Previously, we would only consider a change in host. Now, we consider any change in host, port or scheme to be a change in origin.Patches
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.
Workarounds
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 stream handler backend, rather than curl.
References
For more information
If you have any questions or comments about this advisory, please get in touch with us in
#guzzleon the PHP HTTP Slack. Do not report additional security advisories in that public channel, however - please follow our vulnerability reporting process.CVE-2022-31091
Impact
AuthorizationandCookieheaders on requests are sensitive information. 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 theAuthorizationandCookieheaders from the request, before containing. Previously, we would only consider a change in host or scheme downgrade. Now, we consider any change in host, port or scheme to be a change in origin.Patches
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.
Workarounds
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
For more information
If you have any questions or comments about this advisory, please get in touch with us in
#guzzleon the PHP HTTP Slack. Do not report additional security advisories in that public channel, however please follow our vulnerability reporting process.Release Notes
guzzle/guzzle
### [`v7.4.5`](https://togithub.com/guzzle/guzzle/blob/HEAD/CHANGELOG.md#745---2022-06-20) [Compare Source](https://togithub.com/guzzle/guzzle/compare/7.4.4...7.4.5) ##### Fixed - Fix change in port should be considered a change in origin - Fix `CURLOPT_HTTPAUTH` option not cleared on change of origin ### [`v7.4.4`](https://togithub.com/guzzle/guzzle/blob/HEAD/CHANGELOG.md#744---2022-06-09) [Compare Source](https://togithub.com/guzzle/guzzle/compare/7.4.3...7.4.4) ##### Fixed - Fix failure to strip Authorization header on HTTP downgrade - Fix failure to strip the Cookie header on change in host or HTTP downgradeConfiguration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.