Skip to content

DOS vulnerability on DosFilter

Moderate
joakime published GHSA-7hcf-ppf8-5w5h Oct 14, 2024

Package

maven org.eclipse.jetty.ee10:jetty-ee10-servlets (Maven)

Affected versions

>=12.0.0,<12.0.3

Patched versions

12.0.3
maven org.eclipse.jetty.ee8:jetty-ee8-servlets (Maven)
>=12.0.0,<12.0.3
12.0.3
maven org.eclipse.jetty.ee9:jetty-ee9-servlets (Maven)
>=12.0.0,<12.0.3
12.0.3
maven org.eclipse.jetty:jetty-servlets (Maven)
>=9.0.0,<9.4.54
>=10.0.0,<10.0.18
>=11.0.0,<11.0.18
9.4.54
10.0.18
11.0.18

Description

Description

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 will ultimately exhaust the memory of the server if they have not configured session passivation or an aggressive session inactivation timeout.

Patches

The DoSFilter has been patched in all active releases to no longer support the session tracking mode, even if configured.

Patched releases:

  • 9.4.54
  • 10.0.18
  • 11.0.18
  • 12.0.3

Workarounds

The DoSFilter can be configured to not use sessions for tracking usage by setting the trackSessions init parameter to false. This will then use only the IP tracking mechanism, which is not vulnerable.
Sessions can also be configured to have aggressive passivation or inactivation limits.

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

CVE ID

CVE-2024-9823

Weaknesses

Credits