Update dependency guzzlehttp/guzzle to v6.5.8 [SECURITY] #13
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
6.1.1->6.5.8GitHub Vulnerability Alerts
CVE-2016-5385
PHP through 7.0.8 does not attempt to address RFC 3875 section 4.1.18 namespace conflicts and therefore does not protect applications from the presence of untrusted client data in the HTTP_PROXY environment variable, which might allow remote attackers to redirect an application's outbound HTTP traffic to an arbitrary proxy server via a crafted Proxy header in an HTTP request, as demonstrated by (1) an application that makes a getenv('HTTP_PROXY') call or (2) a CGI configuration of PHP, aka an "httpoxy" issue.
CVE-2022-29248
Impact
Previous version of Guzzle contain a vulnerability with the cookie middleware. The vulnerability is that it is not checked if the cookie domain equals the domain of the server which sets the cookie via the
Set-Cookieheader, allowing a malicious server to set cookies for unrelated domains. For example an attacker atwww.example.commight set a session cookie forapi.example.net, logging the Guzzle client into their account and retrieving private API requests from the security log of their account.Note that our cookie middleware is disabled by default, so most library consumers will not be affected by this issue. Only those who manually add the cookie middleware to the handler stack or construct the client with
['cookies' => true]are affected. Moreover, those who do not use the same Guzzle client to call multiple domains and have disabled redirect forwarding are not affected by this vulnerability.Patches
Affected Guzzle 7 users should upgrade to Guzzle 7.4.3 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.6 or 7.4.3.
Workarounds
If you do not need support for cookies, turn off the cookie middleware. It is already off by default, but if you have turned it on and no longer need it, turn it off.
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-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
v6.5.8Compare Source
See change log for changes.
v6.5.7Compare Source
See change log for changes.
v6.5.6Compare Source
See change log for changes.
v6.5.5Compare Source
v6.5.4Compare Source
v6.5.3Compare Source
v6.5.2Compare Source
v6.5.1Compare Source
v6.5.0Compare Source
curl_multi_init. #2287nullto theheaderoption. #2132RetryMiddlewaredid not do exponential delay between retires due unit mismatch. #2132ClientInterface::VERSIONv6.4.1Compare Source
guzzle.pharwas created in 6.4.0 due expired API token. This release will fix thatparent::__construct()toFileCookieJarandSessionCookieJarv6.4.0Compare Source
RequestException::getResponseBodySummary()#2081GuzzleHttp\Exception\InvalidArgumentException#2163GuzzleHttp\_current_time()to usehrtime()if that function exists. #2242appconnect_timeinTransferStats#2284CookieJar#2335MockHandlerso we can test transfer time #2362v6.3.3Compare Source
v6.3.2Compare Source
v6.3.1Compare Source
v6.3.0Compare Source
on_headersoption in MockHandler #1580read_timeoutoption #1611CURLOPT_CAPATHandCURLOPT_CAINFOproperly #1684\GuzzleHttp\Promise\rejection_forfunction instead of object init #1827v6.2.3Compare Source
v6.2.2Compare Source
v6.2.1Compare Source
https://httpoxy.org/
https://github.com/guzzle/guzzle/pull/14881488
Content-Lengthin PHP StreamHandler to avoid timeouts whena server does not honor
Connection: close.v6.2.0Compare Source
GuzzleHttp\json_encodeandGuzzleHttp\json_decode.https://github.com/guzzle/guzzle/pull/13891389
https://github.com/guzzle/guzzle/pull/13241324
https://github.com/guzzle/guzzle/pull/13731373
https://github.com/guzzle/guzzle/pull/13771377
https://github.com/guzzle/guzzle/pull/14061406
https://github.com/guzzle/guzzle/pull/14091409
https://github.com/guzzle/guzzle/pull/14221422
http_build_queryfor HHVM workaround.https://github.com/guzzle/guzzle/pull/13671367
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.
This PR has been generated by Renovate Bot.