{
  "@id": "urn:uuid:541eec4f-e909-4d70-84b1-ea8b1bba9fe9",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 33,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-10T15:05:51.407283+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-11-03T15:09:27.722120+00:00",
      "status_notes": "Vulnerability CVE-2006-6969 does not affect version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2006-6969 affects Jetty versions before 4.2.27, 5.1.12, 6.0.2, and 6.1.0pre3 (circa 2006), which used predictable java.util.Random for session ID generation. The target version Jetty 9.4.24.v20191120 (November 2019) is 13+ years newer than the affected versions and uses java.security.SecureRandom by default for cryptographically secure session ID generation. The vulnerable code pattern (def...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2006-6969"
      },
      "impact_statement": "not_affected \u2014 CVE-2006-6969 affects Jetty versions before 4.2.27, 5.1.12, 6.0.2, and 6.1.0pre3 (circa 2006), which used predictable java.util.Random for session ID generation. The target version Jetty 9.4.24.v20191120 (November 2019) is 13+ years newer than the affected versions and uses java.security.SecureRandom by default for cryptographically secure session ID generation. The vulnerable code pattern (def..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-11-02T16:42:00.216861+00:00",
      "status_notes": "Vulnerability CVE-2011-4461 does not affect version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2011-4461 (hash collision DoS via unlimited form parameters) is NOT present in Jetty 9.4.24.v20191120. The fix (maxFormKeys limit with default of 1000) was introduced by upstream author Greg Wilkins in commit 085c79d7 on 2011-12-30 and has been present in all Jetty 9.4.x releases since 9.4.0.M0. The target code contains the complete defense: Request.extractFormParameters() obtains maxFormKe...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2011-4461"
      },
      "impact_statement": "not_affected \u2014 CVE-2011-4461 (hash collision DoS via unlimited form parameters) is NOT present in Jetty 9.4.24.v20191120. The fix (maxFormKeys limit with default of 1000) was introduced by upstream author Greg Wilkins in commit 085c79d7 on 2011-12-30 and has been present in all Jetty 9.4.x releases since 9.4.0.M0. The target code contains the complete defense: Request.extractFormParameters() obtains maxFormKe..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-11-06T17:47:26.501853+00:00",
      "status_notes": "Vulnerability CVE-2015-2080 does not affect version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server. Prechecker: An upstream release that contains the fix is part of this version's source history, and the code the fix removes is gone. Version 9.4.24.v20191120 is on a newer release line than any version the advisories list as affected. Advisories: GitHub GHSA-ghgj-3xqr-6jfm (affected up to 9.2.9.v20150224), NVD (affected up to 9.3.0-m1).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2015-2080"
      },
      "impact_statement": "Prechecker: An upstream release that contains the fix is part of this version's source history, and the code the fix removes is gone. Version 9.4.24.v20191120 is on a newer release line than any version the advisories list as affected. Advisories: GitHub GHSA-ghgj-3xqr-6jfm (affected up to 9.2.9.v20150224), NVD (affected up to 9.3.0-m1)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-11-03T15:30:53.892571+00:00",
      "status_notes": "Vulnerability CVE-2016-4800 does not affect version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2016-4800 affects Eclipse Jetty 9.3.x before 9.3.9 on Windows, allowing attackers to bypass protected resource restrictions via URLs with escaped backslash characters. The target version (9.4.24.v20191120) contains the upstream vendor's fix (commit 97af3d663fd) applied by Joakim Erdfelt in May 2016, which was already present in the upstream release that TuxCare onboarded. The fix modifies P...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2016-4800"
      },
      "impact_statement": "not_affected \u2014 CVE-2016-4800 affects Eclipse Jetty 9.3.x before 9.3.9 on Windows, allowing attackers to bypass protected resource restrictions via URLs with escaped backslash characters. The target version (9.4.24.v20191120) contains the upstream vendor's fix (commit 97af3d663fd) applied by Joakim Erdfelt in May 2016, which was already present in the upstream release that TuxCare onboarded. The fix modifies P..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-11-03T12:43:54.437566+00:00",
      "status_notes": "Vulnerability CVE-2017-7656 does not affect version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server. Eclipse Jetty 9.4.24.v20191120 is not affected by CVE-2017-7656. The upstream fix (commit a285deea42fcab60d9edcf994e458c238a348b55, May 17, 2018) was already present in this version when released (November 20, 2019). The fix adds validation to reject HTTP requests with multiple Content-Length headers or both Content-Length and Transfer-Encoding: chunked headers, preventing HTTP request smuggling attacks. The default RFC7230 compliance mode enables these protections. The CVE correctly notes that only 9.4.x versions with non-default RFC2616_LEGACY compliance mode are vulnerable.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 9.3.24.v20180605; >= 9.4.0, < 9.4.11.v20180605), NVD (<= 9.2.26; >= 9.3.0, < 9.3.24; >= 9.4.0, < 9.4.11), Snyk (< 9.3.24.v20180605; >= 9.4.0.M0, < 9.4.11.v20180605; > 8.2.0.v20160908, < 9.3.24.v20180605; >= 9.4.0.M0, < 9.4.11.v20180605).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2017-7656"
      },
      "impact_statement": "Eclipse Jetty 9.4.24.v20191120 is not affected by CVE-2017-7656. The upstream fix (commit a285deea42fcab60d9edcf994e458c238a348b55, May 17, 2018) was already present in this version when released (November 20, 2019). The fix adds validation to reject HTTP requests with multiple Content-Length headers or both Content-Length and Transfer-Encoding: chunked headers, preventing HTTP request smuggling attacks. The default RFC7230 compliance mode enables these protections. The CVE correctly notes that only 9.4.x versions with non-default RFC2616_LEGACY compliance mode are vulnerable.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 9.3.24.v20180605; >= 9.4.0, < 9.4.11.v20180605), NVD (<= 9.2.26; >= 9.3.0, < 9.3.24; >= 9.4.0, < 9.4.11), Snyk (< 9.3.24.v20180605; >= 9.4.0.M0, < 9.4.11.v20180605; > 8.2.0.v20160908, < 9.3.24.v20180605; >= 9.4.0.M0, < 9.4.11.v20180605)."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-10-28T22:44:11.275398+00:00",
      "status_notes": "Vulnerability CVE-2017-7657 affects version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2017-7657"
      },
      "action_statement": "Vulnerability CVE-2017-7657 affects version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-11-03T12:21:26.071673+00:00",
      "status_notes": "Vulnerability CVE-2017-7658 does not affect version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server. The target version 9.4.24.v20191120 is not affected by CVE-2017-7658. The upstream vendor fix (commit a285deea by Greg Wilkins, May 17, 2018) was already present in the upstream release that TuxCare onboarded. The fix prevents HTTP request smuggling by rejecting requests with multiple Content-Length headers or both Content-Length and Transfer-Encoding: chunked headers. The protection is active by default via RFC7230 compliance mode.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 9.2.25.v20180606; >= 9.3.0, < 9.3.24.v20180605; >= 9.4.0, < 9.4.11.v20180605), NVD (<= 9.2.26; >= 9.3.0, < 9.3.24; >= 9.4.0, < 9.4.11), Snyk (> 8.2.0.v20160908, < 9.2.25.v20180606; >= 9.3.0.M0, < 9.3.24.v20180605; >= 9.4.0.M0, < 9.4.11.v20180605).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2017-7658"
      },
      "impact_statement": "The target version 9.4.24.v20191120 is not affected by CVE-2017-7658. The upstream vendor fix (commit a285deea by Greg Wilkins, May 17, 2018) was already present in the upstream release that TuxCare onboarded. The fix prevents HTTP request smuggling by rejecting requests with multiple Content-Length headers or both Content-Length and Transfer-Encoding: chunked headers. The protection is active by default via RFC7230 compliance mode.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 9.2.25.v20180606; >= 9.3.0, < 9.3.24.v20180605; >= 9.4.0, < 9.4.11.v20180605), NVD (<= 9.2.26; >= 9.3.0, < 9.3.24; >= 9.4.0, < 9.4.11), Snyk (> 8.2.0.v20160908, < 9.2.25.v20180606; >= 9.3.0.M0, < 9.3.24.v20180605; >= 9.4.0.M0, < 9.4.11.v20180605)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-11-03T12:33:19.742472+00:00",
      "status_notes": "Vulnerability CVE-2017-9735 does not affect version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server. The target Jetty 9.4.24.v20191120 is NOT vulnerable to CVE-2017-9735 (timing channel attack in Password.java). The fix was already present in the upstream Jetty release that TuxCare onboarded. All password comparisons use constant-time methods (stringEquals/byteEquals) introduced by upstream commit 042f325f1cd (May 2017), which is an ancestor of HEAD and predates the first TuxCare commit (Sept 2025).\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 9.4.0, < 9.4.6.v20170531; >= 9.3.0, < 9.3.20.v20170531; < 9.2.22.v20170606), NVD (< 9.2.22; >= 9.3.0, < 9.3.20; >= 9.4.0, < 9.4.6), Snyk (< 9.2.22.v20170606; >= 9.3.0.M0, < 9.3.20.v20170531; >= 9.4.0.M0, < 9.4.6.v20170531).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2017-9735"
      },
      "impact_statement": "The target Jetty 9.4.24.v20191120 is NOT vulnerable to CVE-2017-9735 (timing channel attack in Password.java). The fix was already present in the upstream Jetty release that TuxCare onboarded. All password comparisons use constant-time methods (stringEquals/byteEquals) introduced by upstream commit 042f325f1cd (May 2017), which is an ancestor of HEAD and predates the first TuxCare commit (Sept 2025).\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 9.4.0, < 9.4.6.v20170531; >= 9.3.0, < 9.3.20.v20170531; < 9.2.22.v20170606), NVD (< 9.2.22; >= 9.3.0, < 9.3.20; >= 9.4.0, < 9.4.6), Snyk (< 9.2.22.v20170606; >= 9.3.0.M0, < 9.3.20.v20170531; >= 9.4.0.M0, < 9.4.6.v20170531)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-10-31T18:12:26.693245+00:00",
      "status_notes": "Vulnerability CVE-2018-12536 does not affect version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2018-12536 is not present in this target. The vulnerability involves server filesystem path disclosure through InvalidPathException when malformed paths (e.g., control characters like %0a) are requested. The upstream Jetty project fixed this in May 2018 (commits 53e8bc2a636, ad4dceb1c08, 65de2c66901) by wrapping exceptions in ResourceContentFactory.getContent() to sanitize error messages, r...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-12536"
      },
      "impact_statement": "not_affected \u2014 CVE-2018-12536 is not present in this target. The vulnerability involves server filesystem path disclosure through InvalidPathException when malformed paths (e.g., control characters like %0a) are requested. The upstream Jetty project fixed this in May 2018 (commits 53e8bc2a636, ad4dceb1c08, 65de2c66901) by wrapping exceptions in ResourceContentFactory.getContent() to sanitize error messages, r..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-11-09T13:56:12.853454+00:00",
      "status_notes": "Vulnerability CVE-2018-12538 does not affect version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server. Prechecker: every line the fix adds is already in this version; the only match was partial, in code of another lineage. Advisories: GitHub (fixed in 9.4.11), NVD (last affected 9.4.8) and Snyk (fixed in 9.4.9) put the fix earlier on this line, and this version is later; the cve.org (Eclipse) record reads as affected only because its range has no upper end.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-12538"
      },
      "impact_statement": "Prechecker: every line the fix adds is already in this version; the only match was partial, in code of another lineage. Advisories: GitHub (fixed in 9.4.11), NVD (last affected 9.4.8) and Snyk (fixed in 9.4.9) put the fix earlier on this line, and this version is later; the cve.org (Eclipse) record reads as affected only because its range has no upper end."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-10-29T00:08:54.384014+00:00",
      "status_notes": "Vulnerability CVE-2018-12545 affects version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2018-12545"
      },
      "action_statement": "Vulnerability CVE-2018-12545 affects version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-10-31T16:14:52.759379+00:00",
      "status_notes": "Vulnerability CVE-2019-10241 does not affect version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server. not_affected \u2014 The target version 9.4.24.v20191120 is NOT vulnerable to CVE-2019-10241. The XSS vulnerability in directory listings was fixed by upstream Eclipse Jetty in commit 7b774d82e82 (April 2019), which was already included in the 9.4.24 release (November 2019). The fix includes: (1) getFileName() method that properly extracts and URL-decodes filenames, preventing full path disclosure; (2) sanitizeXmlS...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-10241"
      },
      "impact_statement": "not_affected \u2014 The target version 9.4.24.v20191120 is NOT vulnerable to CVE-2019-10241. The XSS vulnerability in directory listings was fixed by upstream Eclipse Jetty in commit 7b774d82e82 (April 2019), which was already included in the 9.4.24 release (November 2019). The fix includes: (1) getFileName() method that properly extracts and URL-decodes filenames, preventing full path disclosure; (2) sanitizeXmlS..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-11-02T16:42:00.216861+00:00",
      "status_notes": "Vulnerability CVE-2019-10246 does not affect version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2019-10246 is NOT present in Jetty 9.4.24.v20191120. The vulnerability (exposure of fully qualified filesystem paths in directory listings on Windows) was fixed in upstream Jetty 9.4.17 (April 2019), before the target version 9.4.24 (November 2019). The fix replaced the vulnerable pattern (using getName() with manual substring extraction) with a new getFileName() method that properly extrac...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-10246"
      },
      "impact_statement": "not_affected \u2014 CVE-2019-10246 is NOT present in Jetty 9.4.24.v20191120. The vulnerability (exposure of fully qualified filesystem paths in directory listings on Windows) was fixed in upstream Jetty 9.4.17 (April 2019), before the target version 9.4.24 (November 2019). The fix replaced the vulnerable pattern (using getName() with manual substring extraction) with a new getFileName() method that properly extrac..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-10-31T16:38:00.126365+00:00",
      "status_notes": "Vulnerability CVE-2019-10247 does not affect version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2019-10247 is not present in Jetty 9.4.24.v20191120. The upstream vendor (Eclipse Jetty) fixed this vulnerability in April 2019 (commits 04c994712c0 through a15534d72c0, Issue #3555) by removing the output of context.toString() from DefaultHandler's 404 error page, which was revealing fully qualified directory base resource locations. The fix was included in the upstream 9.4.24.v20191120 re...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-10247"
      },
      "impact_statement": "not_affected \u2014 CVE-2019-10247 is not present in Jetty 9.4.24.v20191120. The upstream vendor (Eclipse Jetty) fixed this vulnerability in April 2019 (commits 04c994712c0 through a15534d72c0, Issue #3555) by removing the output of context.toString() from DefaultHandler's 404 error page, which was revealing fully qualified directory base resource locations. The fix was included in the upstream 9.4.24.v20191120 re..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-11-02T19:16:26.818027+00:00",
      "status_notes": "Vulnerability CVE-2019-17632 does not affect version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server. not_affected \u2014 The target Jetty version 9.4.24.v20191120 is NOT affected by CVE-2019-17632. The vulnerability (unescaped exception messages in text/html and text/json error responses enabling XSS) was fixed in this upstream release through commits 9e40fc9a6fb and cf0df6e3ffd (Issue #4334), which added proper HTML/XML sanitization via StringUtil.sanitizeXmlString(). These fixes were already present in the upst...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-17632"
      },
      "impact_statement": "not_affected \u2014 The target Jetty version 9.4.24.v20191120 is NOT affected by CVE-2019-17632. The vulnerability (unescaped exception messages in text/html and text/json error responses enabling XSS) was fixed in this upstream release through commits 9e40fc9a6fb and cf0df6e3ffd (Issue #4334), which added proper HTML/XML sanitization via StringUtil.sanitizeXmlString(). These fixes were already present in the upst..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-09-30T11:20:05.898576+00:00",
      "status_notes": "Vulnerability CVE-2019-17638 does not affect version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server. CVE-2019-17638 depends on the response-header overflow handling that Eclipse Jetty introduced during the 9.4.27 development cycle. In the affected releases, HttpGenerator signals an oversized response header with a HEADER_OVERFLOW result, and HttpConnection.SendCallback.process() handles it by releasing the header ByteBuffer back to the ByteBufferPool and only afterwards throwing BadMessageException, leaving the field still referencing the released buffer so that the subsequent failure cleanup releases it a second time. The same buffer can then be handed out to two connections at once, and one client receives response data belonging to another. That handling does not exist in 9.4.24.v20191120. HttpGenerator.Result has no HEADER_OVERFLOW value, and generateResponse() deals with an oversized response header entirely within itself: it catches BufferOverflowException and throws BadMessageException(500, \\\"Response header too large\\\") without ever touching the buffer pool (jetty-http/src/main/java/org/eclipse/jetty/http/HttpGenerator.java). In HttpConnection, the header buffer is acquired once at the configured full response-header size \u2014 the generator requests it only when the field is null \u2014 and the entire source tree releases it in exactly one place, SendCallback.release(), which null-checks the field and clears it immediately after releasing. That method is reached only from onCompleteSuccess() or onCompleteFailure(), exactly one of which runs once per response. An overflow therefore yields a single release, and no buffer can be returned to the pool twice. This is consistent with the published advisory, which scopes the vulnerability to 9.4.27.v20200227 through 9.4.29.v20200521 and records the fix in 9.4.30.v20200611.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-17638"
      },
      "impact_statement": "CVE-2019-17638 depends on the response-header overflow handling that Eclipse Jetty introduced during the 9.4.27 development cycle. In the affected releases, HttpGenerator signals an oversized response header with a HEADER_OVERFLOW result, and HttpConnection.SendCallback.process() handles it by releasing the header ByteBuffer back to the ByteBufferPool and only afterwards throwing BadMessageException, leaving the field still referencing the released buffer so that the subsequent failure cleanup releases it a second time. The same buffer can then be handed out to two connections at once, and one client receives response data belonging to another. That handling does not exist in 9.4.24.v20191120. HttpGenerator.Result has no HEADER_OVERFLOW value, and generateResponse() deals with an oversized response header entirely within itself: it catches BufferOverflowException and throws BadMessageException(500, \\\"Response header too large\\\") without ever touching the buffer pool (jetty-http/src/main/java/org/eclipse/jetty/http/HttpGenerator.java). In HttpConnection, the header buffer is acquired once at the configured full response-header size \u2014 the generator requests it only when the field is null \u2014 and the entire source tree releases it in exactly one place, SendCallback.release(), which null-checks the field and clears it immediately after releasing. That method is reached only from onCompleteSuccess() or onCompleteFailure(), exactly one of which runs once per response. An overflow therefore yields a single release, and no buffer can be returned to the pool twice. This is consistent with the published advisory, which scopes the vulnerability to 9.4.27.v20200227 through 9.4.29.v20200521 and records the fix in 9.4.30.v20200611."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-09-30T11:20:05.898576+00:00",
      "status_notes": "Vulnerability CVE-2020-27218 affects version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2020-27218"
      },
      "action_statement": "Vulnerability CVE-2020-27218 affects version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-09-30T11:20:05.898576+00:00",
      "status_notes": "Vulnerability CVE-2020-27223 affects version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2020-27223"
      },
      "action_statement": "Vulnerability CVE-2020-27223 affects version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-09-30T11:20:05.898576+00:00",
      "status_notes": "Vulnerability CVE-2021-28165 is fixed in version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2021-28165"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-09-30T11:34:13.713471+00:00",
      "status_notes": "Vulnerability CVE-2021-34428 is fixed in version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2021-34428"
      }
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-11-10T04:16:00.061099+00:00",
      "status_notes": "Vulnerability CVE-2022-2191 does not affect version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server. Re-checked 2026-11-10 by the vulnerability checker and confirmed by an independent code review: not affected. This version is not affected because its buffer pools do not retain outstanding buffers, so unreleased buffers can be garbage-collected after connection closure instead of accumulating permanently. The pools remove buffers on acquisition and store them only on release (jetty-io/src/main/java/org/eclipse/jetty/io/ArrayByteBufferPool.java:104; jetty-io/src/main/java/org/eclipse/jetty/io/MappedByteBufferPool.java:107). The pool contract explicitly allows garbage collection of unreleased buffers (jetty-io/src/main/java/org/eclipse/jetty/io/ByteBufferPool.java:33).",
      "justification": "vulnerable_code_not_in_execute_path",
      "vulnerability": {
        "name": "CVE-2022-2191"
      },
      "impact_statement": "Re-checked 2026-11-10 by the vulnerability checker and confirmed by an independent code review: not affected. This version is not affected because its buffer pools do not retain outstanding buffers, so unreleased buffers can be garbage-collected after connection closure instead of accumulating permanently. The pools remove buffers on acquisition and store them only on release (jetty-io/src/main/java/org/eclipse/jetty/io/ArrayByteBufferPool.java:104; jetty-io/src/main/java/org/eclipse/jetty/io/MappedByteBufferPool.java:107). The pool contract explicitly allows garbage collection of unreleased buffers (jetty-io/src/main/java/org/eclipse/jetty/io/ByteBufferPool.java:33)."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-09-30T11:20:05.898576+00:00",
      "status_notes": "Vulnerability CVE-2023-26048 affects version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2023-26048"
      },
      "action_statement": "Vulnerability CVE-2023-26048 affects version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-09-30T11:20:05.898576+00:00",
      "status_notes": "Vulnerability CVE-2023-26049 is fixed in version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2023-26049"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-09-30T11:20:05.898576+00:00",
      "status_notes": "Vulnerability CVE-2024-13009 is fixed in version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2024-13009"
      }
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-11-10T04:16:00.061099+00:00",
      "status_notes": "Vulnerability CVE-2024-7708 does not affect version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server. Re-checked 2026-11-10 by the vulnerability checker and confirmed by an independent code review: not affected. This version is not affected because it returns empty request buffers to the pool after zero-byte reads. Both fill callers parse the buffer before acting on a zero-byte result (jetty-server/src/main/java/org/eclipse/jetty/server/HttpConnection.java:251 and :307). Parsing triggers cleanup when no content references remain, and the release guard accepts empty buffers and returns them to the pool (jetty-server/src/main/java/org/eclipse/jetty/server/HttpConnection.java:367 and :215).",
      "vulnerability": {
        "name": "CVE-2024-7708"
      },
      "impact_statement": "Re-checked 2026-11-10 by the vulnerability checker and confirmed by an independent code review: not affected. This version is not affected because it returns empty request buffers to the pool after zero-byte reads. Both fill callers parse the buffer before acting on a zero-byte result (jetty-server/src/main/java/org/eclipse/jetty/server/HttpConnection.java:251 and :307). Parsing triggers cleanup when no content references remain, and the release guard accepts empty buffers and returns them to the pool (jetty-server/src/main/java/org/eclipse/jetty/server/HttpConnection.java:367 and :215)."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-09-30T11:20:05.898576+00:00",
      "status_notes": "Vulnerability CVE-2024-8184 is fixed in version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2024-8184"
      }
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-09-30T11:20:05.898576+00:00",
      "status_notes": "Vulnerability CVE-2026-10051 does not affect version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server. not_affected \u2014 Jetty 9.4.24 is NOT AFFECTED by CVE-2026-10051. The vulnerability exists in Jetty 12.x/11.x where _trailers is a connection-scoped field in HttpConnection that is never reset between requests. In contrast, Jetty 9.4.24 uses a fundamentally different architecture where _trailers is in HttpChannelOverHttp (a channel object that is recycled per-request), and the recycle() method explicitly sets _t...",
      "justification": "vulnerable_code_not_in_execute_path",
      "vulnerability": {
        "name": "CVE-2026-10051"
      },
      "impact_statement": "not_affected \u2014 Jetty 9.4.24 is NOT AFFECTED by CVE-2026-10051. The vulnerability exists in Jetty 12.x/11.x where _trailers is a connection-scoped field in HttpConnection that is never reset between requests. In contrast, Jetty 9.4.24 uses a fundamentally different architecture where _trailers is in HttpChannelOverHttp (a channel object that is recycled per-request), and the recycle() method explicitly sets _t..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-09-30T11:20:05.898576+00:00",
      "status_notes": "Vulnerability CVE-2026-1605 does not affect version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server. Jetty 9.4.24 is not affected by CVE-2026-1605. The vulnerability describes a memory leak specific to Jetty 12.x architecture where GzipRequest objects are created but their destroy() method is not called when only request inflation (no response deflation) occurs. Jetty 9.4.24 uses a completely different architecture without GzipRequest, GzipResponseAndCallback, or the conditional callback wrapping pattern. Instead, it uses GzipHttpInputInterceptor with a recycle-based cleanup mechanism (HttpInput.recycle() \u2192 interceptor.destroy() \u2192 Inflater.end()) that does not exhibit the specific vulnerability pattern described in the CVE.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-1605"
      },
      "impact_statement": "Jetty 9.4.24 is not affected by CVE-2026-1605. The vulnerability describes a memory leak specific to Jetty 12.x architecture where GzipRequest objects are created but their destroy() method is not called when only request inflation (no response deflation) occurs. Jetty 9.4.24 uses a completely different architecture without GzipRequest, GzipResponseAndCallback, or the conditional callback wrapping pattern. Instead, it uses GzipHttpInputInterceptor with a recycle-based cleanup mechanism (HttpInput.recycle() \u2192 interceptor.destroy() \u2192 Inflater.end()) that does not exhibit the specific vulnerability pattern described in the CVE."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-09-30T11:20:05.898576+00:00",
      "status_notes": "Vulnerability CVE-2026-6790 affects version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2026-6790"
      },
      "action_statement": "Vulnerability CVE-2026-6790 affects version 9.4.24.v20191120-tuxcare.5 of org.eclipse.jetty:jetty-server."
    }
  ]
}
