Skip to content

Traefik vulnerable to denial of service with Content-length header

High severity GitHub Reviewed Published Apr 12, 2024 in traefik/traefik • Updated Apr 15, 2024

Package

gomod github.com/traefik/traefik (Go)

Affected versions

<= 2.11.1

Patched versions

2.11.2
gomod github.com/traefik/traefik/v2 (Go)
<= 2.11.1
2.11.2
gomod github.com/traefik/traefik/v3 (Go)
>= 3.0.0-beta3, <= 3.0.0-rc4
3.0.0-rc5

Description

There is a potential vulnerability in Traefik managing requests with Content-length and no body .

Sending a GET request to any Traefik endpoint with the Content-length request header results in an indefinite hang with the default configuration. This vulnerability can be exploited by attackers to induce a denial of service.

Patches

Workarounds

For affected versions, this vulnerability can be mitigated by configuring the readTimeout option.

For more information

If you have any questions or comments about this advisory, please open an issue.

References

@mmatur mmatur published to traefik/traefik Apr 12, 2024
Published to the GitHub Advisory Database Apr 12, 2024
Reviewed Apr 12, 2024
Published by the National Vulnerability Database Apr 12, 2024
Last updated Apr 15, 2024

Severity

High

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
High

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:H

EPSS score

0.045%
(16th percentile)

Weaknesses

CVE ID

CVE-2024-28869

GHSA ID

GHSA-4vwx-54mw-vqfw

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.