Skip to content

← Public intelligence

Maven package

org.eclipse.jetty:jetty-servlets

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

4 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Low, CVSS 2.3MavenPublished

    Eclipse Jetty's PushSessionCacheFilter can cause remote DoS attacks

    CVE-2024-6762 · GHSA-r7m4-f9h5-gr79

    Affected
    • Maven org.eclipse.jetty:jetty-servlets >= 10.0.0, <= 10.0.17; >= 11.0.0, <= 11.0.17; >= 12.0.0, <= 12.0.3
    Fixed in
    12.0.410.0.1811.0.18· Vendor fix available
    Issue
    Impact Jetty PushSessionCacheFilter can be exploited by unauthenticated users to launch remote DoS attacks by exhausting the server’s memory. Patches https://github.com/jetty/jetty.project/pull/9715 https://github.com/jetty/jetty.project/pull/9716 Workarounds The session usage is intrinsic to the design of the PushCacheFilter. The issue can be avoided by: + not using the PushCacheFilter. Push has been deprecated by the various IETF specs and early hints responses should be used instead. + reducing the reducing the idle timeout on unauthenticated sessions will reduce the time such session stay in memory. + configuring a session cache to use session passivation, so that sessions are not stored in memory, but rather in a database or file system that may have significantly more capacity than memory. References https://github.com/jetty/jetty.project/pull/10756 https://github.com/jetty/jetty.project/pull/10755

    Recommended action: Upgrade to 12.0.4, 11.0.18 or 10.0.18 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Medium, CVSS 5.3MavenPublished

    Eclipse Jetty has a denial of service vulnerability on DosFilter

    CVE-2024-9823 · GHSA-j26w-f9rq-mr2q

    Affected
    • Maven org.eclipse.jetty:jetty-servlets >= 9.0.0, < 9.4.54; >= 10.0.0, < 10.0.18; >= 11.0.0, < 11.0.18
    Fixed in
    10.0.1811.0.189.4.54· Vendor fix available
    Issue
    There exists a security vulnerability in Jetty's DosFilter which can be exploited by unauthorized users to cause remote denial-of-service (DoS) attack on the server using DosFilter. By repeatedly sending crafted requests, attackers can trigger OutofMemory errors and exhaust the server's memory finally. Vulnerability details The Jetty DoSFilter (Denial of Service Filter) is a security filter designed to protect web applications against certain types of Denial of Service (DoS) attacks and other abusive behavior. It helps to mitigate excessive resource consumption by limiting the rate at which clients can make requests to the server. The DoSFilter monitors and tracks client request patterns, including request rates, and can take actions such as blocking or delaying requests from clients that exceed predefined thresholds. The internal tracking of requests in DoSFilter is the source of this OutOfMemory condition. Impact Users of the DoSFilter may be subject to DoS attacks that…

    Recommended action: Upgrade to 11.0.18, 10.0.18 or 9.4.54 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  3. Low, CVSS 3.5MavenPublished

    Jetty vulnerable to errant command quoting in CGI Servlet

    CVE-2023-36479 · GHSA-3gh6-v5v9-6v9j

    Affected
    • Maven org.eclipse.jetty:jetty-servlets >= 9.0.0, <= 9.4.51; >= 10.0.0, <= 10.0.15; >= 11.0.0, <= 11.0.15
    Fixed in
    9.4.5210.0.1611.0.16· Vendor fix available
    Issue
    If a user sends a request to a org.eclipse.jetty.servlets.CGI Servlet for a binary with a space in its name, the servlet will escape the command by wrapping it in quotation marks. This wrapped command, plus an optional command prefix, will then be executed through a call to Runtime.exec. If the original binary name provided by the user contains a quotation mark followed by a space, the resulting command line will contain multiple tokens instead of one. For example, if a request references a binary called file” name “here, the escaping algorithm will generate the command line string “file” name “here”, which will invoke the binary named file, not the one that the user requested. Exploit Scenario The cgi-bin directory contains a binary named exec and a subdirectory named exec” commands, which contains a file called bin1. The user sends to the CGI servlet a request for the filename exec” commands/bin1. This request will pass the file existence check on lines 194 through 205. The servlet…

    Recommended action: Upgrade to 11.0.16, 10.0.16 or 9.4.52 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  4. Medium, CVSS 5.3MavenPublished

    Jetty Utility Servlets ConcatServlet Double Decoding Information Disclosure Vulnerability

    CVE-2021-28169 · GHSA-gwcr-j4wh-j3cq

    Affected
    • Maven org.eclipse.jetty:jetty-servlets <= 9.4.40; >= 10.0.0, <= 10.0.2; >= 11.0.0, <= 11.0.2
    Fixed in
    9.4.4111.0.310.0.3· Vendor fix available
    Issue
    Requests to the ConcatServlet and WelcomeFilter are able to access protected resources within the WEB-INF directory. For example a request to the ConcatServlet with a URI of /concat?/%2557EB-INF/web.xml can retrieve the web.xml file. This can reveal sensitive information regarding the implementation of a web application. This occurs because both ConcatServlet and WelcomeFilter decode the supplied path to verify it is not within the WEB-INF or META-INF directories. It then uses this decoded path to call RequestDispatcher which will also do decoding of the path. This double decoding allows paths with a doubly encoded WEB-INF to bypass this security check. Impact This affects all versions of ConcatServlet and WelcomeFilter in versions before 9.4.41, 10.0.3 and 11.0.3. Workarounds If you cannot update to the latest version of Jetty, you can instead deploy your own version of the ConcatServlet and/or the WelcomeFilter by using the code from the latest version of Jetty.

    Recommended action: Upgrade to 11.0.3, 10.0.3 or 9.4.41 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →