Skip to content

Traefik affected by Go HTTP Request Smuggling Vulnerability

Critical severity GitHub Reviewed Published Apr 18, 2025 in traefik/traefik • Updated Apr 18, 2025

Package

gomod github.com/traefik/traefik/v2 (Go)

Affected versions

< 2.11.24

Patched versions

2.11.24
gomod github.com/traefik/traefik/v3 (Go)
< 3.3.6
= 3.4.0-rc1
3.3.6
3.4.0-rc2

Description

Summary

net/http: request smuggling through invalid chunked data: The net/http package accepts data in the chunked transfer encoding containing an invalid chunk-size line terminated by a bare LF. When used in conjunction with a server or proxy which incorrectly interprets a bare LF in a chunk extension as part of the extension, this could permit request smuggling. [CVE-2025-22871] Vendor Affected Components: Go: 1.23.x < 1.23.8

More Details: CVE-2025-22871

Patches

References

@emilevauge emilevauge published to traefik/traefik Apr 18, 2025
Published to the GitHub Advisory Database Apr 18, 2025
Reviewed Apr 18, 2025
Last updated Apr 18, 2025

Severity

Critical

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
High
Integrity
High
Availability
None

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:H/I:H/A:N

EPSS score

Weaknesses

CVE ID

No known CVE

GHSA ID

GHSA-5423-jcjm-2gpv

Source code

Credits

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