https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 18:15:42 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-233969 EUVD-2026-233969 https://cve.radiocsirt.org/vuln/euvd-2026-233969 https://cve.radiocsirt.org/vuln/fkie_cve-2022-31090 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2022-31090 https://cve.radiocsirt.org/vuln/ghsa-25mq-v84q-4j7r <p><strong>Affected:</strong> Packagist: guzzlehttp/guzzle</p> <p>### Impact</p> <p>`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.</p> <p>### Patches</p> <p>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.</p> <p>### Workarounds</p> <p>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.</p> <p>### References</p> <p>* [RFC9110 Section 15.4](https://www.rfc-editor.org/rfc/rfc9110.html#name-redirection-3xx) * [CVE-2022-27776](https://curl.se/docs/CVE-2022-27776.html)</p> <p>### For more information</p> <p>If you have any questions or comments about this advisory, please get in touch with us…</p> <p><strong>Affected:</strong> Packagist: guzzlehttp/guzzle</p> <p>### Impact</p> <p>`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.</p> <p>### Patches</p> <p>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.</p> <p>### Workarounds</p> <p>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.</p> <p>### References</p> <p>* [RFC9110 Section 15.4](https://www.rfc-editor.org/rfc/rfc9110.html#name-redirection-3xx) * [CVE-2022-27776](https://curl.se/docs/CVE-2022-27776.html)</p> <p>### For more information</p> <p>If you have any questions or comments about this advisory, please get in touch with us…</p> https://cve.radiocsirt.org/vuln/ghsa-25mq-v84q-4j7r https://cve.radiocsirt.org/vuln/gsd-2022-31090 gsd-2022-31090 https://cve.radiocsirt.org/vuln/gsd-2022-31090 https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-31090 <p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: civicrm, Ubuntu:Pro:18.04:LTS: civicrm, Ubuntu:18.04:LTS: mediawiki, Ubuntu:Pro:20.04:LTS: civicrm, Ubuntu:Pro:20.04:LTS: mediawiki, Ubuntu:22.04:LTS: icinga-php-thirdparty, Ubuntu:22.04:LTS: icingaweb2-module-reactbundle, Ubuntu:Pro:22.04:LTS: civicrm, Ubuntu:Pro:22.04:LTS: mediawiki, Ubuntu:24.04:LTS: icinga-php-thirdparty and 5 more</p> <p>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.</p> <p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: civicrm, Ubuntu:Pro:18.04:LTS: civicrm, Ubuntu:18.04:LTS: mediawiki, Ubuntu:Pro:20.04:LTS: civicrm, Ubuntu:Pro:20.04:LTS: mediawiki, Ubuntu:22.04:LTS: icinga-php-thirdparty, Ubuntu:22.04:LTS: icingaweb2-module-reactbundle, Ubuntu:Pro:22.04:LTS: civicrm, Ubuntu:Pro:22.04:LTS: mediawiki, Ubuntu:24.04:LTS: icinga-php-thirdparty and 5 more</p> <p>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.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-31090