{
  "@id": "urn:uuid:382fd32b-4968-4c08-9dd0-1cc132d9e32a",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 6,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-10T04:15:11.464324+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T12:00:43.890125+00:00",
      "status_notes": "Vulnerability CVE-2006-6969 does not affect version 9.4.50.v20221201-tuxcare.6 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2006-6969 affects Jetty versions that use java.util.Random for session ID generation. The target repository (Jetty 9.4.50.v20221201) contains the upstream fix that replaced Random with SecureRandom, which has been in the Jetty codebase since March 2009. The vulnerable code pattern is not present in this version.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2006-6969"
      },
      "impact_statement": "not_affected \u2014 CVE-2006-6969 affects Jetty versions that use java.util.Random for session ID generation. The target repository (Jetty 9.4.50.v20221201) contains the upstream fix that replaced Random with SecureRandom, which has been in the Jetty codebase since March 2009. The vulnerable code pattern is not present in this version."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T12:00:43.890125+00:00",
      "status_notes": "Vulnerability CVE-2011-4461 does not affect version 9.4.50.v20221201-tuxcare.6 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2011-4461 addresses hash collision DoS via unbounded form parameter parsing in Jetty 8.1.0.RC2 and earlier. The target version (9.4.50.v20221201) is NOT vulnerable. The upstream vendor (Eclipse Jetty) applied the fix in commit 085c79d7d6c (author: Greg Wilkins <gregw@webtide.com>), which was already present in the upstream release 9.4.50.v20221201 before TuxCare onboarded it. The fix limits...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2011-4461"
      },
      "impact_statement": "not_affected \u2014 CVE-2011-4461 addresses hash collision DoS via unbounded form parameter parsing in Jetty 8.1.0.RC2 and earlier. The target version (9.4.50.v20221201) is NOT vulnerable. The upstream vendor (Eclipse Jetty) applied the fix in commit 085c79d7d6c (author: Greg Wilkins <gregw@webtide.com>), which was already present in the upstream release 9.4.50.v20221201 before TuxCare onboarded it. The fix limits..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-06T17:45:44.119017+00:00",
      "status_notes": "Vulnerability CVE-2015-2080 does not affect version 9.4.50.v20221201-tuxcare.6 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.50.v20221201 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.50.v20221201 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.50.v20221201-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T12:00:43.890125+00:00",
      "status_notes": "Vulnerability CVE-2016-4800 does not affect version 9.4.50.v20221201-tuxcare.6 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2016-4800 affects Jetty 9.3.x before 9.3.9 (Windows path normalization bypass via escaped backslashes). The target version 9.4.50.v20221201 is NOT affected because the upstream fix (commit 97af3d663fd, May 2016) was already present in the upstream release when TuxCare onboarded this version. The fix adds dual-layer protection: (1) URI comparison in checkAliasPath() to detect aliasing before...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2016-4800"
      },
      "impact_statement": "not_affected \u2014 CVE-2016-4800 affects Jetty 9.3.x before 9.3.9 (Windows path normalization bypass via escaped backslashes). The target version 9.4.50.v20221201 is NOT affected because the upstream fix (commit 97af3d663fd, May 2016) was already present in the upstream release when TuxCare onboarded this version. The fix adds dual-layer protection: (1) URI comparison in checkAliasPath() to detect aliasing before..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T12:00:43.890125+00:00",
      "status_notes": "Vulnerability CVE-2017-7656 does not affect version 9.4.50.v20221201-tuxcare.6 of org.eclipse.jetty:jetty-server. CVE-2017-7656 HTTP Request Smuggling vulnerability is not present in Jetty 9.4.50.v20221201. The upstream vendor fix (commit a285deea42f by Greg Wilkins, May 2018) was already included in the upstream release before TuxCare onboarded this version. The fix adds comprehensive protections against request smuggling: detection of conflicting Content-Length/Transfer-Encoding headers, multiple Content-Length headers, and chunk length overflow. These protections are enabled by default via RFC7230 compliance mode.\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": "CVE-2017-7656 HTTP Request Smuggling vulnerability is not present in Jetty 9.4.50.v20221201. The upstream vendor fix (commit a285deea42f by Greg Wilkins, May 2018) was already included in the upstream release before TuxCare onboarded this version. The fix adds comprehensive protections against request smuggling: detection of conflicting Content-Length/Transfer-Encoding headers, multiple Content-Length headers, and chunk length overflow. These protections are enabled by default via RFC7230 compliance mode.\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.50.v20221201-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T12:00:43.890125+00:00",
      "status_notes": "Vulnerability CVE-2017-7657 affects version 9.4.50.v20221201-tuxcare.6 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2017-7657"
      },
      "action_statement": "Vulnerability CVE-2017-7657 affects version 9.4.50.v20221201-tuxcare.6 of org.eclipse.jetty:jetty-server."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T12:00:43.890125+00:00",
      "status_notes": "Vulnerability CVE-2017-7658 does not affect version 9.4.50.v20221201-tuxcare.6 of org.eclipse.jetty:jetty-server. CVE-2017-7658 (HTTP Request Smuggling via duplicate Content-Length headers or mixed Content-Length/Transfer-Encoding headers) is NOT present in target version 9.4.50.v20221201. The upstream fix (commit a285deea42fc by Greg Wilkins, dated 2018-05-17) was already included in the upstream release before TuxCare onboarded this version. The fix uses a compliance framework to reject ambiguous content-length scenarios: _hasContentLength flag tracks header occurrence, throwing BadMessageException on duplicates (MULTIPLE_CONTENT_LENGTHS) and rejecting mixed Transfer-Encoding+Content-Length (TRANSFER_ENCODING_WITH_CONTENT_LENGTH). Protection is active by default under 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": "CVE-2017-7658 (HTTP Request Smuggling via duplicate Content-Length headers or mixed Content-Length/Transfer-Encoding headers) is NOT present in target version 9.4.50.v20221201. The upstream fix (commit a285deea42fc by Greg Wilkins, dated 2018-05-17) was already included in the upstream release before TuxCare onboarded this version. The fix uses a compliance framework to reject ambiguous content-length scenarios: _hasContentLength flag tracks header occurrence, throwing BadMessageException on duplicates (MULTIPLE_CONTENT_LENGTHS) and rejecting mixed Transfer-Encoding+Content-Length (TRANSFER_ENCODING_WITH_CONTENT_LENGTH). Protection is active by default under 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.50.v20221201-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T12:00:43.890125+00:00",
      "status_notes": "Vulnerability CVE-2017-9735 does not affect version 9.4.50.v20221201-tuxcare.6 of org.eclipse.jetty:jetty-server. CVE-2017-9735 timing channel vulnerability is NOT present in target version 9.4.50.v20221201. The vulnerable short-circuiting password comparison code was fixed in upstream Jetty 9.4.10.v20180503 (May 2018), well before this version. The target contains constant-time comparison methods (stringEquals, byteEquals) that prevent timing attacks by processing all character positions regardless of mismatches and using modulo arithmetic to hide length differences. Fix authored by upstream developer Simone Bordet, shipped in the upstream release that TuxCare onboarded.\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": "CVE-2017-9735 timing channel vulnerability is NOT present in target version 9.4.50.v20221201. The vulnerable short-circuiting password comparison code was fixed in upstream Jetty 9.4.10.v20180503 (May 2018), well before this version. The target contains constant-time comparison methods (stringEquals, byteEquals) that prevent timing attacks by processing all character positions regardless of mismatches and using modulo arithmetic to hide length differences. Fix authored by upstream developer Simone Bordet, shipped in the upstream release that TuxCare onboarded.\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.50.v20221201-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T12:00:43.890125+00:00",
      "status_notes": "Vulnerability CVE-2018-12536 does not affect version 9.4.50.v20221201-tuxcare.6 of org.eclipse.jetty:jetty-server. not_affected \u2014 The target repository (Jetty 9.4.50.v20221201) is NOT affected by CVE-2018-12536. The vulnerability, which allowed server file system paths to be disclosed in error responses when processing malformed HTTP requests, was fixed by upstream Jetty developers in May 2018 (commits 53e8bc2a636, 65de2c66901, ad4dceb1c08). This fix was already present in the 9.4.50.v20221201 release when TuxCare onboard...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-12536"
      },
      "impact_statement": "not_affected \u2014 The target repository (Jetty 9.4.50.v20221201) is NOT affected by CVE-2018-12536. The vulnerability, which allowed server file system paths to be disclosed in error responses when processing malformed HTTP requests, was fixed by upstream Jetty developers in May 2018 (commits 53e8bc2a636, 65de2c66901, ad4dceb1c08). This fix was already present in the 9.4.50.v20221201 release when TuxCare onboard..."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T12:00:43.890125+00:00",
      "status_notes": "Vulnerability CVE-2018-12538 affects version 9.4.50.v20221201-tuxcare.6 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2018-12538"
      },
      "action_statement": "Vulnerability CVE-2018-12538 affects version 9.4.50.v20221201-tuxcare.6 of org.eclipse.jetty:jetty-server."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T12:00:43.890125+00:00",
      "status_notes": "Vulnerability CVE-2018-12545 affects version 9.4.50.v20221201-tuxcare.6 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2018-12545"
      },
      "action_statement": "Vulnerability CVE-2018-12545 affects version 9.4.50.v20221201-tuxcare.6 of org.eclipse.jetty:jetty-server."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T12:00:43.890125+00:00",
      "status_notes": "Vulnerability CVE-2019-10241 does not affect version 9.4.50.v20221201-tuxcare.6 of org.eclipse.jetty:jetty-server. not_affected \u2014 The target repository (Jetty 9.4.50.v20221201) is NOT vulnerable to CVE-2019-10241. The XSS vulnerability in directory listings was fixed in upstream commit 7b774d82e82 (April 2019) which was already included in the upstream release 9.4.50.v20221201 that TuxCare onboarded. The fix replaced the vulnerable pattern that used getName() and manual path parsing with a new getFileName() method that pr...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-10241"
      },
      "impact_statement": "not_affected \u2014 The target repository (Jetty 9.4.50.v20221201) is NOT vulnerable to CVE-2019-10241. The XSS vulnerability in directory listings was fixed in upstream commit 7b774d82e82 (April 2019) which was already included in the upstream release 9.4.50.v20221201 that TuxCare onboarded. The fix replaced the vulnerable pattern that used getName() and manual path parsing with a new getFileName() method that pr..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T12:00:43.890125+00:00",
      "status_notes": "Vulnerability CVE-2019-10246 does not affect version 9.4.50.v20221201-tuxcare.6 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2019-10246 affects Jetty versions 9.2.27, 9.3.26, and 9.4.16, causing information disclosure of fully qualified directory paths in directory listings on Windows. The target version 9.4.50.v20221201 includes the upstream fix (commit 7b774d82e82) that was already present in the release before TuxCare onboarding. The fix replaces the vulnerable getName() usage with a new getFileName() method t...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-10246"
      },
      "impact_statement": "not_affected \u2014 CVE-2019-10246 affects Jetty versions 9.2.27, 9.3.26, and 9.4.16, causing information disclosure of fully qualified directory paths in directory listings on Windows. The target version 9.4.50.v20221201 includes the upstream fix (commit 7b774d82e82) that was already present in the release before TuxCare onboarding. The fix replaces the vulnerable getName() usage with a new getFileName() method t..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T12:00:43.890125+00:00",
      "status_notes": "Vulnerability CVE-2019-10247 does not affect version 9.4.50.v20221201-tuxcare.6 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2019-10247 is NOT present in Jetty 9.4.50.v20221201. The vulnerability (disclosure of base resource directory paths in 404 error pages) was fixed in upstream Jetty 9.4.17 (April 2019), over three years before version 9.4.50 (December 2022). The fix commits are present in HEAD's ancestry and the vulnerable code pattern (context.toString() output in DefaultHandler) is absent from the target.",
      "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.50.v20221201. The vulnerability (disclosure of base resource directory paths in 404 error pages) was fixed in upstream Jetty 9.4.17 (April 2019), over three years before version 9.4.50 (December 2022). The fix commits are present in HEAD's ancestry and the vulnerable code pattern (context.toString() output in DefaultHandler) is absent from the target."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T12:00:43.890125+00:00",
      "status_notes": "Vulnerability CVE-2019-17632 does not affect version 9.4.50.v20221201-tuxcare.6 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2019-17632 is NOT present in Jetty 9.4.50.v20221201. The vulnerability affected versions 9.4.21-9.4.23 (released in late 2019) where exception messages in error responses were not escaped, enabling XSS attacks. The upstream vendor (Joakim Erdfelt) fixed this in commit cf0df6e3ffd on November 20, 2019 by adding StringUtil.sanitizeXmlString() calls to escape HTML/XML entities in exception mes...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-17632"
      },
      "impact_statement": "not_affected \u2014 CVE-2019-17632 is NOT present in Jetty 9.4.50.v20221201. The vulnerability affected versions 9.4.21-9.4.23 (released in late 2019) where exception messages in error responses were not escaped, enabling XSS attacks. The upstream vendor (Joakim Erdfelt) fixed this in commit cf0df6e3ffd on November 20, 2019 by adding StringUtil.sanitizeXmlString() calls to escape HTML/XML entities in exception mes..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T12:00:43.890125+00:00",
      "status_notes": "Vulnerability CVE-2019-17638 does not affect version 9.4.50.v20221201-tuxcare.6 of org.eclipse.jetty:jetty-server. The target Jetty 9.4.50.v20221201 is NOT affected by CVE-2019-17638. The vulnerability (double-release of ByteBuffer leading to information disclosure) was fixed by upstream Eclipse Jetty in commit ff8ae56fa93 (June 2020, first released in 9.4.30.v20200611), well before the target version 9.4.50.v20221201 (December 2022). The fix was authored by Greg Wilkins (gregw@webtide.com), an upstream Eclipse Jetty developer, and was already included in the upstream release that TuxCare onboarded. All fix characteristics are present in the current code: _chunk field moved from instance-level to SendCallback local scope, releaseHeader() and releaseChunk() helper methods that null references after releasing, and HEADER_OVERFLOW checks capacity before releasing the buffer.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 9.4.27, < 9.4.30.v20200611), NVD (= 9.4.27-20200227; = 9.4.28-20200408; = 9.4.29-20200521), Snyk (>= 9.4.27.v20200227, < 9.4.30.v20200611).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-17638"
      },
      "impact_statement": "The target Jetty 9.4.50.v20221201 is NOT affected by CVE-2019-17638. The vulnerability (double-release of ByteBuffer leading to information disclosure) was fixed by upstream Eclipse Jetty in commit ff8ae56fa93 (June 2020, first released in 9.4.30.v20200611), well before the target version 9.4.50.v20221201 (December 2022). The fix was authored by Greg Wilkins (gregw@webtide.com), an upstream Eclipse Jetty developer, and was already included in the upstream release that TuxCare onboarded. All fix characteristics are present in the current code: _chunk field moved from instance-level to SendCallback local scope, releaseHeader() and releaseChunk() helper methods that null references after releasing, and HEADER_OVERFLOW checks capacity before releasing the buffer.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 9.4.27, < 9.4.30.v20200611), NVD (= 9.4.27-20200227; = 9.4.28-20200408; = 9.4.29-20200521), Snyk (>= 9.4.27.v20200227, < 9.4.30.v20200611)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T12:00:43.890125+00:00",
      "status_notes": "Vulnerability CVE-2020-27218 does not affect version 9.4.50.v20221201-tuxcare.6 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2020-27218 (GZIP request body inflation vulnerability) is NOT present in target version 9.4.50.v20221201. The upstream fix was already included in the Jetty 9.4.35.v20201120 release (November 2020) and is present in the target. The fix adds defense mechanisms to either consume all unconsumed request input or set Connection: close to prevent connection reuse, blocking the attack chain where ...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2020-27218"
      },
      "impact_statement": "not_affected \u2014 CVE-2020-27218 (GZIP request body inflation vulnerability) is NOT present in target version 9.4.50.v20221201. The upstream fix was already included in the Jetty 9.4.35.v20201120 release (November 2020) and is present in the target. The fix adds defense mechanisms to either consume all unconsumed request input or set Connection: close to prevent connection reuse, blocking the attack chain where ..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T12:00:43.890125+00:00",
      "status_notes": "Vulnerability CVE-2020-27223 does not affect version 9.4.50.v20221201-tuxcare.6 of org.eclipse.jetty:jetty-server. not_affected \u2014 The target Jetty version 9.4.50.v20221201 is NOT affected by CVE-2020-27223. The vulnerability was fixed in upstream Jetty version 9.4.37.v20210219 (February 2021) via commit 10e531756b9, and this fix was already present in the 9.4.50.v20221201 release (December 2022) that TuxCare onboarded. The vulnerable inefficient bubble-sort algorithm in QuotedQualityCSV.java that caused CPU exhaustion has...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2020-27223"
      },
      "impact_statement": "not_affected \u2014 The target Jetty version 9.4.50.v20221201 is NOT affected by CVE-2020-27223. The vulnerability was fixed in upstream Jetty version 9.4.37.v20210219 (February 2021) via commit 10e531756b9, and this fix was already present in the 9.4.50.v20221201 release (December 2022) that TuxCare onboarded. The vulnerable inefficient bubble-sort algorithm in QuotedQualityCSV.java that caused CPU exhaustion has..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T12:00:43.890125+00:00",
      "status_notes": "Vulnerability CVE-2021-28165 does not affect version 9.4.50.v20221201-tuxcare.6 of org.eclipse.jetty:jetty-server. Target version 9.4.50.v20221201 is NOT AFFECTED by CVE-2021-28165. The vulnerability (infinite CPU loop when processing large TLS frames >17408 bytes) was fixed in upstream Jetty 9.4.38.v20210224 by commit 294b2ba02b6 (authored by Simone Bordet on 2021-03-22). The fix adds a buffer space check before continuing the SSL unwrap loop, preventing the infinite loop condition. Since the target version 9.4.50 (December 2022) is much later than 9.4.38 (February 2021), the fix was already present in the upstream release that TuxCare onboarded. The vulnerable code pattern does not exist in the target.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 7.2.2, < 9.4.39; >= 10.0.0, < 10.0.2; >= 11.0.0, < 11.0.2), NVD (>= 7.2.2, < 9.4.39; >= 10.0.0, < 10.0.2; >= 11.0.0, < 11.0.2), Snyk (>= 7.2.2.v20101205, < 9.4.39.v20210325; >= 10.0.0.alpha0, < 10.0.2; >= 11.0.0.alpha0, < 11.0.2).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2021-28165"
      },
      "impact_statement": "Target version 9.4.50.v20221201 is NOT AFFECTED by CVE-2021-28165. The vulnerability (infinite CPU loop when processing large TLS frames >17408 bytes) was fixed in upstream Jetty 9.4.38.v20210224 by commit 294b2ba02b6 (authored by Simone Bordet on 2021-03-22). The fix adds a buffer space check before continuing the SSL unwrap loop, preventing the infinite loop condition. Since the target version 9.4.50 (December 2022) is much later than 9.4.38 (February 2021), the fix was already present in the upstream release that TuxCare onboarded. The vulnerable code pattern does not exist in the target.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 7.2.2, < 9.4.39; >= 10.0.0, < 10.0.2; >= 11.0.0, < 11.0.2), NVD (>= 7.2.2, < 9.4.39; >= 10.0.0, < 10.0.2; >= 11.0.0, < 11.0.2), Snyk (>= 7.2.2.v20101205, < 9.4.39.v20210325; >= 10.0.0.alpha0, < 10.0.2; >= 11.0.0.alpha0, < 11.0.2)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T12:00:43.890125+00:00",
      "status_notes": "Vulnerability CVE-2021-34428 does not affect version 9.4.50.v20221201-tuxcare.6 of org.eclipse.jetty:jetty-server. Version 9.4.50.v20221201 is not affected by CVE-2021-34428: the security fix is already present in the target branch. Momus prerequisite check: \"All 1 patch commits already exist in target branch\". No backport needed.",
      "vulnerability": {
        "name": "CVE-2021-34428"
      },
      "impact_statement": "Version 9.4.50.v20221201 is not affected by CVE-2021-34428: the security fix is already present in the target branch. Momus prerequisite check: \"All 1 patch commits already exist in target branch\". No backport needed."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-10T04:15:11.464324+00:00",
      "status_notes": "Vulnerability CVE-2022-2191 does not affect version 9.4.50.v20221201-tuxcare.6 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 pool does not retain acquired buffers, allowing unreleased buffers to be garbage-collected after failed connections close. In jetty-io/src/main/java/org/eclipse/jetty/io/ByteBufferPool.java:181, acquisition removes buffers from the queue; line 208 adds them back only on release. Failed fills close the underlying endpoint at jetty-io/src/main/java/org/eclipse/jetty/io/ssl/SslConnection.java:845.",
      "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 pool does not retain acquired buffers, allowing unreleased buffers to be garbage-collected after failed connections close. In jetty-io/src/main/java/org/eclipse/jetty/io/ByteBufferPool.java:181, acquisition removes buffers from the queue; line 208 adds them back only on release. Failed fills close the underlying endpoint at jetty-io/src/main/java/org/eclipse/jetty/io/ssl/SslConnection.java:845."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T12:00:43.890125+00:00",
      "status_notes": "Vulnerability CVE-2023-26048 is fixed in version 9.4.50.v20221201-tuxcare.6 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2023-26048"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T12:00:43.890125+00:00",
      "status_notes": "Vulnerability CVE-2023-26049 is fixed in version 9.4.50.v20221201-tuxcare.6 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2023-26049"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T12:00:43.890125+00:00",
      "status_notes": "Vulnerability CVE-2024-13009 is fixed in version 9.4.50.v20221201-tuxcare.6 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.50.v20221201-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-10T04:14:20.974341+00:00",
      "status_notes": "Vulnerability CVE-2024-7708 does not affect version 9.4.50.v20221201-tuxcare.6 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 empty request buffers are returned to the pool after zero-byte reads, preventing the memory leak. Parsing releases the buffer when no content references remain (jetty-server/src/main/java/org/eclipse/jetty/server/HttpConnection.java:387). The release clears the connection\u2019s reference and returns the empty buffer to its pool (jetty-server/src/main/java/org/eclipse/jetty/server/HttpConnection.java:224).",
      "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 empty request buffers are returned to the pool after zero-byte reads, preventing the memory leak. Parsing releases the buffer when no content references remain (jetty-server/src/main/java/org/eclipse/jetty/server/HttpConnection.java:387). The release clears the connection\u2019s reference and returns the empty buffer to its pool (jetty-server/src/main/java/org/eclipse/jetty/server/HttpConnection.java:224)."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T12:00:43.890125+00:00",
      "status_notes": "Vulnerability CVE-2024-8184 is fixed in version 9.4.50.v20221201-tuxcare.6 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.50.v20221201-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T12:00:43.890125+00:00",
      "status_notes": "Vulnerability CVE-2026-10051 does not affect version 9.4.50.v20221201-tuxcare.6 of org.eclipse.jetty:jetty-server. not_affected \u2014 Jetty 9.4.50.v20221201 is not affected by CVE-2026-10051. While the CVE describes a cross-request trailer leakage vulnerability in Jetty 12+, this target version uses a different architecture where the fix has been present since July 2017 (commit be1eb26670f). The _trailers field is properly cleared in HttpChannel.recycle() (line 418) and HttpChannelOverHttp.recycle() (line 89), which are calle...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-10051"
      },
      "impact_statement": "not_affected \u2014 Jetty 9.4.50.v20221201 is not affected by CVE-2026-10051. While the CVE describes a cross-request trailer leakage vulnerability in Jetty 12+, this target version uses a different architecture where the fix has been present since July 2017 (commit be1eb26670f). The _trailers field is properly cleared in HttpChannel.recycle() (line 418) and HttpChannelOverHttp.recycle() (line 89), which are calle..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T12:00:43.890125+00:00",
      "status_notes": "Vulnerability CVE-2026-1605 does not affect version 9.4.50.v20221201-tuxcare.6 of org.eclipse.jetty:jetty-server. Version 9.4.50.v20221201 is not vulnerable. Summary: Target repository is Jetty 9.4.50.v20221201, which predates the vulnerable Jetty 12.x architecture. CVE-2026-1605 specifically affects Jetty versions 12.0.0-12.0.31 and 12.1.0-12.1.5 with their new Content API and GzipRequest implementation. The target uses a completely different architecture for gzip request handling. [terminalized not_affected from patch_application_manual/not_vulnerable]",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-1605"
      },
      "impact_statement": "Version 9.4.50.v20221201 is not vulnerable. Summary: Target repository is Jetty 9.4.50.v20221201, which predates the vulnerable Jetty 12.x architecture. CVE-2026-1605 specifically affects Jetty versions 12.0.0-12.0.31 and 12.1.0-12.1.5 with their new Content API and GzipRequest implementation. The target uses a completely different architecture for gzip request handling. [terminalized not_affected from patch_application_manual/not_vulnerable]"
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.50.v20221201-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T12:01:44.104854+00:00",
      "status_notes": "Vulnerability CVE-2026-6790 is fixed in version 9.4.50.v20221201-tuxcare.6 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2026-6790"
      }
    }
  ]
}
