Skip to content

Commit

Permalink
Publish Advisories
Browse files Browse the repository at this point in the history
  • Loading branch information
advisory-database[bot] committed Jul 12, 2022
1 parent 133ef93 commit 00dd5bf
Show file tree
Hide file tree
Showing 7 changed files with 31 additions and 6 deletions.
@@ -1,15 +1,18 @@
{
"schema_version": "1.2.0",
"id": "GHSA-25mq-v84q-4j7r",
"modified": "2022-06-21T16:57:10Z",
"modified": "2022-07-12T21:58:38Z",
"published": "2022-06-21T16:57:10Z",
"aliases": [
"CVE-2022-31090"
],
"summary": "CURLOPT_HTTPAUTH option not cleared on change of origin",
"details": "### Impact\n\n`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.\n\n### Patches\n\nAffected 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.\n\n### Workarounds\n\nIf 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.\n\n### References\n\n* [RFC9110 Section 15.4](https://www.rfc-editor.org/rfc/rfc9110.html#name-redirection-3xx)\n* [CVE-2022-27776](https://curl.se/docs/CVE-2022-27776.html)\n\n### For more information\n\nIf you have any questions or comments about this advisory, please get in touch with us in `#guzzle` on the [PHP HTTP Slack](https://php-http.slack.com/). Do not report additional security advisories in that public channel, however - please follow our [vulnerability reporting process](https://github.com/guzzle/guzzle/security/policy).\n",
"severity": [

{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N"
}
],
"affected": [
{
Expand Down
@@ -1,15 +1,18 @@
{
"schema_version": "1.2.0",
"id": "GHSA-q559-8m2m-g699",
"modified": "2022-06-21T20:07:16Z",
"modified": "2022-07-12T21:58:57Z",
"published": "2022-06-21T20:07:16Z",
"aliases": [
"CVE-2022-31091"
],
"summary": "Change in port should be considered a change in origin",
"details": "### Impact\n\n`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.\n\n### Patches\n\nAffected 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.\n\n### Workarounds\n\nAn 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.\n\n### References\n\n* [RFC9110 Section 15.4](https://www.rfc-editor.org/rfc/rfc9110.html#name-redirection-3xx)\n* [CVE-2022-27776](https://curl.se/docs/CVE-2022-27776.html)\n\n### For more information\n\nIf you have any questions or comments about this advisory, please get in touch with us in `#guzzle` on the [PHP HTTP Slack](https://php-http.slack.com/). Do not report additional security advisories in that public channel, however - please follow our [vulnerability reporting process](https://github.com/guzzle/guzzle/security/policy).\n",
"severity": [

{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N"
}
],
"affected": [
{
Expand Down
@@ -1,15 +1,18 @@
{
"schema_version": "1.2.0",
"id": "GHSA-v78m-2q7v-fjqp",
"modified": "2022-06-22T17:52:51Z",
"modified": "2022-07-12T21:59:11Z",
"published": "2022-06-22T17:52:51Z",
"aliases": [
"CVE-2022-31099"
],
"summary": "Uncontrolled Recursion in rulex",
"details": "### Impact\nWhen parsing untrusted rulex expressions, the stack may overflow, possibly enabling a Denial of Service attack. This happens when parsing an expression with several hundred levels of nesting, causing the process to abort immediately.\n\nThis is a security concern for you, if\n- your service parses untrusted rulex expressions (expressions provided by an untrusted user), and\n- your service becomes unavailable when the process running rulex aborts due to a stack overflow.\n\n### Patches\nThe crash is fixed in version **0.4.3**. Affected users are advised to update to this version.\n\n### Workarounds\nNone.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [rulex](https://github.com/rulex-rs/rulex/issues)\n* Email me at [ludwig.stecher@gmx.de](mailto:ludwig.stecher@gmx.de)\n\n### Credits\n\nCredit for finding these bugs goes to\n\n- [evanrichter](https://github.com/evanrichter)\n- [ForAllSecure Mayhem](https://forallsecure.com/)\n- [cargo fuzz](https://github.com/rust-fuzz/cargo-fuzz) and [afl.rs](https://github.com/rust-fuzz/afl.rs)",
"severity": [

{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
}
],
"affected": [
{
Expand Down
Expand Up @@ -78,6 +78,10 @@
"type": "WEB",
"url": "https://github.com/kubeedge/kubeedge/security/advisories/GHSA-qpx3-9565-5xwm"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-31078"
},
{
"type": "PACKAGE",
"url": "https://github.com/kubeedge/kubeedge"
Expand Down
Expand Up @@ -78,6 +78,10 @@
"type": "WEB",
"url": "https://github.com/kubeedge/kubeedge/security/advisories/GHSA-vwm6-qc77-v2rh"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-31073"
},
{
"type": "WEB",
"url": "https://github.com/kubeedge/kubeedge/pull/4038"
Expand Down
Expand Up @@ -78,6 +78,10 @@
"type": "WEB",
"url": "https://github.com/kubeedge/kubeedge/security/advisories/GHSA-w52j-3457-q9wr"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-31074"
},
{
"type": "PACKAGE",
"url": "github.com/kubeedge/kubeedge"
Expand Down
Expand Up @@ -78,6 +78,10 @@
"type": "WEB",
"url": "https://github.com/kubeedge/kubeedge/security/advisories/GHSA-x3px-2p95-f6jr"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-31075"
},
{
"type": "PACKAGE",
"url": "github.com/kubeedge/kubeedge"
Expand Down

0 comments on commit 00dd5bf

Please sign in to comment.