{
  "@id": "urn:uuid:d3646db0-279a-49f1-b941-78b50e635898",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 24,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-04T09:10:25.284357+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty.http2/http2-server@11.0.18-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty.http2/http2-server@11.0.18-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-04T09:10:25.284357+00:00",
      "status_notes": "Vulnerability CVE-2022-2048 does not affect version 11.0.18-tuxcare.1 of org.eclipse.jetty.http2:http2-server. CVE-2022-2048 is NOT present in the target Jetty 11.0.18 repository. The vulnerability involved blocking selector threads when handling invalid HTTP/2 requests, causing denial of service. The fix, which defers error response writing to a separate thread by returning error handling as a Runnable, is present in both HTTP/2 and HTTP/3 components. This fix was authored by upstream (Simone Bordet) and shipped in the upstream release before TuxCare's involvement.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 9.4.47; >= 10.0.0, < 10.0.10; >= 11.0.0, < 11.0.10), NVD (< 9.4.47; >= 10.0.0, < 10.0.9; >= 11.0.0, < 11.0.9), Snyk (< 9.4.47; >= 10.0.0-alpha0, < 10.0.10; >= 11.0.0-alpha0, < 11.0.10).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2022-2048"
      },
      "impact_statement": "CVE-2022-2048 is NOT present in the target Jetty 11.0.18 repository. The vulnerability involved blocking selector threads when handling invalid HTTP/2 requests, causing denial of service. The fix, which defers error response writing to a separate thread by returning error handling as a Runnable, is present in both HTTP/2 and HTTP/3 components. This fix was authored by upstream (Simone Bordet) and shipped in the upstream release before TuxCare's involvement.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 9.4.47; >= 10.0.0, < 10.0.10; >= 11.0.0, < 11.0.10), NVD (< 9.4.47; >= 10.0.0, < 10.0.9; >= 11.0.0, < 11.0.9), Snyk (< 9.4.47; >= 10.0.0-alpha0, < 10.0.10; >= 11.0.0-alpha0, < 11.0.10)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty.http2/http2-server@11.0.18-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty.http2/http2-server@11.0.18-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-04T09:05:53.304095+00:00",
      "status_notes": "Vulnerability CVE-2023-44487 does not affect version 11.0.18-tuxcare.1 of org.eclipse.jetty.http2:http2-server. The target repository (Jetty 11.0.18-tuxcare.1) is NOT AFFECTED by CVE-2023-44487 (HTTP/2 Rapid Reset attack). The vulnerability fix was already present in the upstream Jetty 11.0.18 release that TuxCare onboarded. The fix adds rate control to RST_STREAM frame processing (128 events/second limit) to prevent resource exhaustion attacks where clients rapidly send and reset streams. The rate control code is present in ResetBodyParser.java and other HTTP/2 parser files, blocking the attack vector described in the CVE.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 9.3.0, < 9.4.53; >= 10.0.0, < 10.0.17; >= 11.0.0, < 11.0.17; >= 9.3.0, < 9.4.53; >= 10.0.0, < 10.0.17; >= 11.0.0, < 11.0.17), NVD (< 9.4.53; >= 10.0.0, < 10.0.17; >= 11.0.0, < 11.0.17; >= 12.0.0, < 12.0.2), Snyk (< 9.4.53.v20231009; >= 10.0.0, < 10.0.17; >= 11.0.0, < 11.0.17).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2023-44487"
      },
      "impact_statement": "The target repository (Jetty 11.0.18-tuxcare.1) is NOT AFFECTED by CVE-2023-44487 (HTTP/2 Rapid Reset attack). The vulnerability fix was already present in the upstream Jetty 11.0.18 release that TuxCare onboarded. The fix adds rate control to RST_STREAM frame processing (128 events/second limit) to prevent resource exhaustion attacks where clients rapidly send and reset streams. The rate control code is present in ResetBodyParser.java and other HTTP/2 parser files, blocking the attack vector described in the CVE.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 9.3.0, < 9.4.53; >= 10.0.0, < 10.0.17; >= 11.0.0, < 11.0.17; >= 9.3.0, < 9.4.53; >= 10.0.0, < 10.0.17; >= 11.0.0, < 11.0.17), NVD (< 9.4.53; >= 10.0.0, < 10.0.17; >= 11.0.0, < 11.0.17; >= 12.0.0, < 12.0.2), Snyk (< 9.4.53.v20231009; >= 10.0.0, < 10.0.17; >= 11.0.0, < 11.0.17)."
    }
  ]
}