{
  "@id": "urn:uuid:bd2fa8b9-bc97-439e-bd98-9ce24040d0d5",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 28,
  "@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.26-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty.http2/http2-server@11.0.26-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-04T09:10:25.284357+00:00",
      "status_notes": "Vulnerability CVE-2022-2048 does not affect version 11.0.26-tuxcare.1 of org.eclipse.jetty.http2:http2-server. CVE-2022-2048 does not affect Jetty 11.0.26-tuxcare.3. The vulnerability involved synchronous error handling on the selector thread that could block when invalid HTTP/2 requests caused flow control exhaustion. The upstream fix (commit b705091afb9) was already present in Jetty 11.0.26 before TuxCare onboarded it. Both HttpChannelOverHTTP2.java and HttpChannelOverHTTP3.java contain the fix: error handlers return Runnable lambdas `() -> onBadMessage(x)` instead of calling onBadMessage() directly, preventing selector thread blocking. The vulnerable code pattern is not present in this version.\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 does not affect Jetty 11.0.26-tuxcare.3. The vulnerability involved synchronous error handling on the selector thread that could block when invalid HTTP/2 requests caused flow control exhaustion. The upstream fix (commit b705091afb9) was already present in Jetty 11.0.26 before TuxCare onboarded it. Both HttpChannelOverHTTP2.java and HttpChannelOverHTTP3.java contain the fix: error handlers return Runnable lambdas `() -> onBadMessage(x)` instead of calling onBadMessage() directly, preventing selector thread blocking. The vulnerable code pattern is not present in this version.\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.26-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty.http2/http2-server@11.0.26-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-04T09:03:00.104314+00:00",
      "status_notes": "Vulnerability CVE-2023-44487 does not affect version 11.0.26-tuxcare.1 of org.eclipse.jetty.http2:http2-server. The target repository (Jetty 11.0.26-tuxcare.3) is NOT AFFECTED by CVE-2023-44487 (HTTP/2 Rapid Reset). All required fixes for rate control on HTTP/2 control frames (RST_STREAM, CONTINUATION, SETTINGS, PUSH_PROMISE) and header block fragment capacity limits are present in the code. The fix was authored by Simone Bordet (upstream Jetty developer) in commit 0f246d12090 on 2023-10-09 and was included in the upstream Jetty 11.0.26 release. When TuxCare onboarded version 11.0.26 (setup commit 804520a9c0c on 2025-12-12), the fix was already present in the upstream code. This is an upstream fix, not a TuxCare backport.\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.26-tuxcare.3) is NOT AFFECTED by CVE-2023-44487 (HTTP/2 Rapid Reset). All required fixes for rate control on HTTP/2 control frames (RST_STREAM, CONTINUATION, SETTINGS, PUSH_PROMISE) and header block fragment capacity limits are present in the code. The fix was authored by Simone Bordet (upstream Jetty developer) in commit 0f246d12090 on 2023-10-09 and was included in the upstream Jetty 11.0.26 release. When TuxCare onboarded version 11.0.26 (setup commit 804520a9c0c on 2025-12-12), the fix was already present in the upstream code. This is an upstream fix, not a TuxCare backport.\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)."
    }
  ]
}