{
  "@id": "urn:uuid:3c83e7f4-a147-4f67-bf07-e1bf23fb6f95",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 20,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-04T09:15:51.446651+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty.http2/jetty-http2-common@12.0.22-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty.http2/jetty-http2-common@12.0.22-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-27T20:16:57.791784+00:00",
      "status_notes": "Vulnerability CVE-2007-1651 does not affect version 12.0.22-tuxcare.1 of org.eclipse.jetty.http2:jetty-http2-common. Target Jetty 12.0.22 is NOT affected. The CVE concerns a CSRF / session-restoration weakness in Jetty's OpenID Connect support; the two vendor patches (5f2c96dc, 2020 \u2014 move ID-token expiry to initial-auth-only + proper logout/validate delegation; e9f260f4, 2021 \u2014 replace the single anti-forgery CSRF token with a per-session, SecureRandom-keyed csrfMap and mandatory `state` validation) are UPSTREAM Jetty fixes authored by lachlan@webtide.com years before the 12.0.22 release (June 2025). Both fix commits are ancestors of HEAD, and the shipped jetty-core/jetty-openid and jetty-ee9/jetty-ee9-openid modules contain the complete post-fix code. The pre-fix vulnerable pattern (single CSRF_TOKEN setAttribute, isExpired() gating session validity, empty logout()) is absent. Not a TuxCare backport \u2014 the fix is native/upstream, so verdict is not_affected (justification code_not_present), not already_fixed.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2007-1651"
      },
      "impact_statement": "Target Jetty 12.0.22 is NOT affected. The CVE concerns a CSRF / session-restoration weakness in Jetty's OpenID Connect support; the two vendor patches (5f2c96dc, 2020 \u2014 move ID-token expiry to initial-auth-only + proper logout/validate delegation; e9f260f4, 2021 \u2014 replace the single anti-forgery CSRF token with a per-session, SecureRandom-keyed csrfMap and mandatory `state` validation) are UPSTREAM Jetty fixes authored by lachlan@webtide.com years before the 12.0.22 release (June 2025). Both fix commits are ancestors of HEAD, and the shipped jetty-core/jetty-openid and jetty-ee9/jetty-ee9-openid modules contain the complete post-fix code. The pre-fix vulnerable pattern (single CSRF_TOKEN setAttribute, isExpired() gating session validity, empty logout()) is absent. Not a TuxCare backport \u2014 the fix is native/upstream, so verdict is not_affected (justification code_not_present), not already_fixed."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty.http2/jetty-http2-common@12.0.22-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty.http2/jetty-http2-common@12.0.22-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-27T20:16:57.791784+00:00",
      "status_notes": "Vulnerability CVE-2007-1652 affects version 12.0.22-tuxcare.1 of org.eclipse.jetty.http2:jetty-http2-common.",
      "vulnerability": {
        "name": "CVE-2007-1652"
      },
      "action_statement": "Vulnerability CVE-2007-1652 affects version 12.0.22-tuxcare.1 of org.eclipse.jetty.http2:jetty-http2-common."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty.http2/jetty-http2-common@12.0.22-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty.http2/jetty-http2-common@12.0.22-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-04T09:15:51.446651+00:00",
      "status_notes": "Vulnerability CVE-2023-44487 does not affect version 12.0.22-tuxcare.1 of org.eclipse.jetty.http2:jetty-http2-common. The target (Jetty 12.0.22) is NOT AFFECTED by CVE-2023-44487. The upstream fix for the HTTP/2 Rapid Reset vulnerability was already present in the Jetty 12.0.22 release when TuxCare onboarded it. All required defenses are in place: (1) rate limiting on RST_STREAM, SETTINGS, and CONTINUATION frames at 128 events/second, (2) buffer capacity limits on header block fragment accumulation, (3) connection termination with ENHANCE_YOUR_CALM_ERROR for rate violations. The fix was authored by Simone Bordet (upstream Jetty maintainer) in October 2023 and shipped in the upstream release.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 12.0.0, < 12.0.2; >= 12.0.0, < 12.0.2), NVD (< 9.4.53; >= 10.0.0, < 10.0.17; >= 11.0.0, < 11.0.17; >= 12.0.0, < 12.0.2).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2023-44487"
      },
      "impact_statement": "The target (Jetty 12.0.22) is NOT AFFECTED by CVE-2023-44487. The upstream fix for the HTTP/2 Rapid Reset vulnerability was already present in the Jetty 12.0.22 release when TuxCare onboarded it. All required defenses are in place: (1) rate limiting on RST_STREAM, SETTINGS, and CONTINUATION frames at 128 events/second, (2) buffer capacity limits on header block fragment accumulation, (3) connection termination with ENHANCE_YOUR_CALM_ERROR for rate violations. The fix was authored by Simone Bordet (upstream Jetty maintainer) in October 2023 and shipped in the upstream release.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 12.0.0, < 12.0.2; >= 12.0.0, < 12.0.2), NVD (< 9.4.53; >= 10.0.0, < 10.0.17; >= 11.0.0, < 11.0.17; >= 12.0.0, < 12.0.2)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty.http2/jetty-http2-common@12.0.22-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty.http2/jetty-http2-common@12.0.22-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-04T09:15:51.446651+00:00",
      "status_notes": "Vulnerability CVE-2024-22201 does not affect version 12.0.22-tuxcare.1 of org.eclipse.jetty.http2:jetty-http2-common. CVE-2024-22201: The target Jetty 12.0.22-tuxcare.1 is NOT AFFECTED. The vulnerability (HTTP/2 connection not closed after idle timeout when TCP congested) was fixed in upstream commit 0839a208cdc by Simone Bordet on 2024-01-15. This fix was included in the upstream 12.0.22 release before TuxCare onboarded it (commit 11545e1f96a on 2024-11-02). Both HTTP/2 (HTTP2Session.java lines 2154-2202) and HTTP/3 (HTTP3Session.java lines 557-573) contain the complete fix: the onIdleTimeout() method now forcibly terminates connections in CLOSED/CLOSING states by calling flusher.abort() or terminateAndDisconnect(), preventing indefinite file descriptor leaks during TCP congestion.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 12.0.0, < 12.0.6; >= 12.0.0, < 12.0.6), NVD (>= 9.3.0, < 9.4.54; >= 10.0.0, < 10.0.20; >= 11.0.0, < 11.0.20; >= 12.0.0, < 12.0.6), cve.org (>= 9.3.0, <= 9.4.53; >= 10.0.0, <= 10.0.19; >= 11.0.0, <= 11.0.19; >= 12.0.0, <= 12.0.5; >= 9.3.0, <= 9.4.53; >= 10.0.0, <= 10.0.19; >= 11.0.0, <= 11.0.19; >= 12.0.0, <= 12.0.5), Snyk (>= 12.0.0, < 12.0.6; >= 12.0.0, < 12.0.6; >= 12.0.0, < 12.0.6; >= 12.0.0, < 12.0.6).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2024-22201"
      },
      "impact_statement": "CVE-2024-22201: The target Jetty 12.0.22-tuxcare.1 is NOT AFFECTED. The vulnerability (HTTP/2 connection not closed after idle timeout when TCP congested) was fixed in upstream commit 0839a208cdc by Simone Bordet on 2024-01-15. This fix was included in the upstream 12.0.22 release before TuxCare onboarded it (commit 11545e1f96a on 2024-11-02). Both HTTP/2 (HTTP2Session.java lines 2154-2202) and HTTP/3 (HTTP3Session.java lines 557-573) contain the complete fix: the onIdleTimeout() method now forcibly terminates connections in CLOSED/CLOSING states by calling flusher.abort() or terminateAndDisconnect(), preventing indefinite file descriptor leaks during TCP congestion.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 12.0.0, < 12.0.6; >= 12.0.0, < 12.0.6), NVD (>= 9.3.0, < 9.4.54; >= 10.0.0, < 10.0.20; >= 11.0.0, < 11.0.20; >= 12.0.0, < 12.0.6), cve.org (>= 9.3.0, <= 9.4.53; >= 10.0.0, <= 10.0.19; >= 11.0.0, <= 11.0.19; >= 12.0.0, <= 12.0.5; >= 9.3.0, <= 9.4.53; >= 10.0.0, <= 10.0.19; >= 11.0.0, <= 11.0.19; >= 12.0.0, <= 12.0.5), Snyk (>= 12.0.0, < 12.0.6; >= 12.0.0, < 12.0.6; >= 12.0.0, < 12.0.6; >= 12.0.0, < 12.0.6)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty.http2/jetty-http2-common@12.0.22-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty.http2/jetty-http2-common@12.0.22-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-04T09:15:51.446651+00:00",
      "status_notes": "Vulnerability CVE-2025-1948 does not affect version 12.0.22-tuxcare.1 of org.eclipse.jetty.http2:jetty-http2-common. CVE-2025-1948 affects Eclipse Jetty 12.0.0-12.0.16 where HTTP/2 clients can specify arbitrarily large SETTINGS_MAX_HEADER_LIST_SIZE values causing OOM. The target version 12.0.22-tuxcare.1 contains the upstream fix from Jetty 12.0.17 (commit 8414f79a9c4) that caps remote peer values to the server's configured maximum and validates positive values. The vulnerable code pattern is not present because the upstream vendor (Ludovic Orban) fixed it before TuxCare onboarded version 12.0.22.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 12.0.0, < 12.0.17), NVD (>= 12.0.0, < 12.0.17), cve.org (>= 12.0.0, <= 12.0.16), Snyk (>= 12.0.0, < 12.0.17; >= 12.0.0, < 12.0.17).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2025-1948"
      },
      "impact_statement": "CVE-2025-1948 affects Eclipse Jetty 12.0.0-12.0.16 where HTTP/2 clients can specify arbitrarily large SETTINGS_MAX_HEADER_LIST_SIZE values causing OOM. The target version 12.0.22-tuxcare.1 contains the upstream fix from Jetty 12.0.17 (commit 8414f79a9c4) that caps remote peer values to the server's configured maximum and validates positive values. The vulnerable code pattern is not present because the upstream vendor (Ludovic Orban) fixed it before TuxCare onboarded version 12.0.22.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 12.0.0, < 12.0.17), NVD (>= 12.0.0, < 12.0.17), cve.org (>= 12.0.0, <= 12.0.16), Snyk (>= 12.0.0, < 12.0.17; >= 12.0.0, < 12.0.17)."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty.http2/jetty-http2-common@12.0.22-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty.http2/jetty-http2-common@12.0.22-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-27T20:18:00.127363+00:00",
      "status_notes": "Vulnerability CVE-2025-5115 is fixed in version 12.0.22-tuxcare.1 of org.eclipse.jetty.http2:jetty-http2-common.",
      "vulnerability": {
        "name": "CVE-2025-5115"
      }
    }
  ]
}
