Publish Advisories

GHSA-x5rv-w9pm-8qp8
GHSA-rggv-cv7r-mw98
GHSA-8p25-3q46-8q2p

advisories/github-reviewed/2023/03/GHSA-x5rv-w9pm-8qp8/GHSA-x5rv-w9pm-8qp8.json

@@ -1,13 +1,13 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-x5rv-w9pm-8qp8",
-  "modified": "2025-01-31T14:21:39Z",
+  "modified": "2025-02-07T20:45:09Z",
   "published": "2023-03-01T19:17:17Z",
   "aliases": [
     "CVE-2023-0092"
   ],
   "summary": "Juju controller - Arbitrary file reading vulnerability",
-  "details": "### Impact\nAn authenticated user who has read access to the juju controller model, may construct a remote request to download an arbitrary file from the controller's filesystem.\n\n### Patches\nPatched in juju 2.9.38 and juju 3.0.3\n[juju/juju#ef803e2](https://github.com/juju/juju/commit/ef803e2a13692d355b784b7da8b4b1f01dab1556)\n\n### Workarounds\nLimit read access to the controller model to only trusted users.\n",
+  "details": "### Impact\nAn authenticated user who has read access to the juju controller model, may construct a remote request to download an arbitrary file from the controller's filesystem.\n\n### Patches\nPatched in juju 2.9.38 and juju 3.0.3\n[juju/juju#ef803e2](https://github.com/juju/juju/commit/ef803e2a13692d355b784b7da8b4b1f01dab1556)\n\n### Workarounds\nLimit read access to the controller model to only trusted users.",
   "severity": [
     {
       "type": "CVSS_V3",
@@ -71,6 +71,10 @@
       "type": "WEB",
       "url": "https://bugs.launchpad.net/juju/+bug/1999622"
     },
+    {
+      "type": "ADVISORY",
+      "url": "https://github.com/advisories/GHSA-x5rv-w9pm-8qp8"
+    },
     {
       "type": "PACKAGE",
       "url": "https://github.com/juju/juju"
@@ -78,6 +82,7 @@
   ],
   "database_specific": {
     "cwe_ids": [
+      "CWE-22",
       "CWE-73"
     ],
     "severity": "MODERATE",

advisories/github-reviewed/2024/02/GHSA-rggv-cv7r-mw98/GHSA-rggv-cv7r-mw98.json

@@ -1,13 +1,13 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-rggv-cv7r-mw98",
-  "modified": "2024-05-02T18:38:17Z",
+  "modified": "2025-02-07T20:44:34Z",
   "published": "2024-02-26T20:13:46Z",
   "aliases": [
     "CVE-2024-22201"
   ],
   "summary": "Connection leaking on idle timeout when TCP congested",
-  "details": "### Impact\nIf an HTTP/2 connection gets TCP congested, when an idle timeout occurs the HTTP/2 session is marked as closed, and then a GOAWAY frame is queued to be written.\nHowever it is not written because the connection is TCP congested.\nWhen another idle timeout period elapses, it is then supposed to hard close the connection, but it delegates to the HTTP/2 session which reports that it has already been closed so it does not attempt to hard close the connection.\n\nThis leaves the connection in ESTABLISHED state (i.e. not closed), TCP congested, and idle.\n\nAn attacker can cause many connections to end up in this state, and the server may run out of file descriptors, eventually causing the server to stop accepting new connections from valid clients.\n\nThe client may also be impacted (if the server does not read causing a TCP congestion), but the issue is more severe for servers.\n\n### Patches\nPatched versions:\n* 9.4.54\n* 10.0.20\n* 11.0.20\n* 12.0.6\n\n### Workarounds\nDisable HTTP/2 and HTTP/3 support until you can upgrade to a patched version of Jetty.\nHTTP/1.x is not affected.\n\n### References\n* https://github.com/jetty/jetty.project/issues/11256.\n",
+  "details": "### Impact\nIf an HTTP/2 connection gets TCP congested, when an idle timeout occurs the HTTP/2 session is marked as closed, and then a GOAWAY frame is queued to be written.\nHowever it is not written because the connection is TCP congested.\nWhen another idle timeout period elapses, it is then supposed to hard close the connection, but it delegates to the HTTP/2 session which reports that it has already been closed so it does not attempt to hard close the connection.\n\nThis leaves the connection in ESTABLISHED state (i.e. not closed), TCP congested, and idle.\n\nAn attacker can cause many connections to end up in this state, and the server may run out of file descriptors, eventually causing the server to stop accepting new connections from valid clients.\n\nThe client may also be impacted (if the server does not read causing a TCP congestion), but the issue is more severe for servers.\n\n### Patches\nPatched versions:\n* 9.4.54\n* 10.0.20\n* 11.0.20\n* 12.0.6\n\n### Workarounds\nDisable HTTP/2 and HTTP/3 support until you can upgrade to a patched version of Jetty.\nHTTP/1.x is not affected.\n\n### References\n* https://github.com/jetty/jetty.project/issues/11256.",
   "severity": [
     {
       "type": "CVSS_V3",
@@ -214,7 +214,8 @@
   ],
   "database_specific": {
     "cwe_ids": [
-      "CWE-400"
+      "CWE-400",
+      "CWE-770"
     ],
     "severity": "HIGH",
     "github_reviewed": true,