Jetty vulnerabilitiesAnd the versions its exploited flaws hit.

Product1 known exploited358 versions
The short answer

Jetty is made by Eclipse. We track 39 published vulnerabilities in it, across 358 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 10 October 2023. If you run Jetty, check your version against the exploited flaws below and patch those first.

Check your version

The most recent Jetty flaw added to the known-exploited list is CVE-2023-44487, on 10 October 2023. We keep watching the known-exploited list.

Versions

Which versions of Jetty do the exploited flaws hit?

Each exploited flaw lists the versions it affects, usually as ranges. "before 9.4.53" means every version up to, but not including, 9.4.53. Find your version, then patch.

  • CVE-2023-44487Exploited list, 10 Oct 2023

    HTTP/2 Rapid Reset Attack Vulnerability

    before 9.4.5310.0.0 to before 10.0.1711.0.0 to before 11.0.1712.0.0 to before 12.0.2
Known exploited

Which Jetty vulnerabilities are being exploited?

1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.

  1. 7.5
    CVE-2023-44487HighKnown exploited
    HTTP/2 Rapid Reset Attack Vulnerability

    HTTP/2 contains a rapid reset vulnerability that allows for a distributed denial-of-service attack (DDoS).

    Chance of use>99%Known exploited since10 Oct 2023
Exploit likelihood

Which Jetty flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. >99%
    CVE-2023-44487HighKnown exploited

    The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.

    CVSS7.5Published10 Oct 2023
  2. >99%

    For Eclipse Jetty versions 9.4.37-9.4.42, 10.0.1-10.0.5 & 11.0.1-11.0.5, URIs can be crafted using some encoded characters to access the content of the WEB-INF directory and/or bypass some security constraints.

    CVSS5.3Published15 Jul 2021
  3. 82%

    In Eclipse Jetty 9.4.37.v20210219 to 9.4.38.v20210224, the default compliance mode allows requests with URIs that contain %2e or %2e%2e segments to access protected resources within the WEB-INF directory.

    CVSS5.3Published1 Apr 2021
  4. 78%

    For Eclipse Jetty versions <= 9.4.40, <= 10.0.2, <= 11.0.2, it is possible for requests to the ConcatServlet with a doubly encoded path to access protected resources within the WEB-INF directory.

    CVSS5.3Published9 Jun 2021
  5. 78%

    In Eclipse Jetty 9.4.6.v20170531 to 9.4.36.v20210114 (inclusive), 10.0.0, and 11.0.0 when Jetty handles a request containing multiple Accept headers with a large number of “quality” (i.e.

    CVSS5.2Published26 Feb 2021
  6. 75%

    The exception handling code in Eclipse Jetty before 9.2.9.v20150224 allows remote attackers to obtain sensitive information from process memory via illegal characters in an HTTP header, aka JetLeak.

    CVSS7.5Published7 Oct 2016
  7. 54%

    In Eclipse Jetty 7.2.2 to 9.4.38, 10.0.0.alpha0 to 10.0.1, and 11.0.0.alpha0 to 11.0.1, CPU usage can reach 100% upon receiving a large invalid TLS frame.

    CVSS7.5Published1 Apr 2021
  8. 15%

    In Eclipse Jetty, versions 9.2.x and older, 9.3.x (all configurations), and 9.4.x (non-default configuration with RFC2616 compliance enabled), transfer-encoding chunks are handled poorly.

    CVSS9.8Published26 Jun 2018
  9. 11%

    In Eclipse Jetty, versions 9.4.27.v20200227 to 9.4.29.v20200521, in case of too large response headers, Jetty throws an exception to produce an HTTP 431 error.

    CVSS9.4Published9 Jul 2020
Precursor Intelligence

Running Jetty? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 39 published vulnerabilities listed under the name Jetty, across 358 versions. The most recent Jetty flaw added to the known-exploited list is CVE-2023-44487, on 10 October 2023.

1 is on the list of flaws known to be exploited. The most recently added is CVE-2023-44487.

Each flaw names its own versions, usually as ranges. The newest, CVE-2023-44487, affects before 9.4.53, 10.0.0 to before 10.0.17, 11.0.0 to before 11.0.17, 12.0.0 to before 12.0.2. The versions for every exploited flaw are listed on this page.

Create a Precursor Intelligence account and track Jetty. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.