{
  "@id": "urn:uuid:b122fdfc-b121-4083-82e0-38e73dc07303",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 25,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-02T17:58:00.190834+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-openid@12.0.22-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-openid@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:jetty-openid. 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/jetty-openid@12.0.22-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-openid@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:jetty-openid.",
      "vulnerability": {
        "name": "CVE-2007-1652"
      },
      "action_statement": "Vulnerability CVE-2007-1652 affects version 12.0.22-tuxcare.1 of org.eclipse.jetty:jetty-openid."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-openid@12.0.22-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-openid@12.0.22-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-02T17:58:00.190834+00:00",
      "status_notes": "Vulnerability CVE-2023-41900 does not affect version 12.0.22-tuxcare.1 of org.eclipse.jetty:jetty-openid. not_affected \u2014 CVE-2023-41900 is NOT present in Jetty 12.0.22-tuxcare.1. The vulnerability pattern (where a revoked authentication object is returned to the current request) is absent because the upstream fix was already included in the Jetty 12.0.22 release that TuxCare onboarded. The fix commit 24b7d06fd5ce5468caa3eaa93688879fb2900fda (authored by lachlan@webtide.com) moved the `return authenticationState;`...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2023-41900"
      },
      "impact_statement": "not_affected \u2014 CVE-2023-41900 is NOT present in Jetty 12.0.22-tuxcare.1. The vulnerability pattern (where a revoked authentication object is returned to the current request) is absent because the upstream fix was already included in the Jetty 12.0.22 release that TuxCare onboarded. The fix commit 24b7d06fd5ce5468caa3eaa93688879fb2900fda (authored by lachlan@webtide.com) moved the `return authenticationState;`..."
    }
  ]
}
