HAProxy
HAProxy 3 before 3.4.6 allows a remote unauthenticated attacker to cause a denial of service (persistent worker-thread CPU exhaustion) via an HTTP/1.1 chunked request. Although the H1 multiplexer drains the request before closing the stream, the parser repeatedly re-processes the same bytes without making progress. The affected thread stays busy at 100% CPU after timeouts expire and after the client disconnects, and repeated requests can consume all worker threads until the process is restarted.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 3.0.0, < 3.0.30
- >= 3.2.0, < 3.2.26
- >= 3.3.0, < 3.3.17
- >= 3.4.0, < 3.4.6
- >= 3.5-dev, < 3.5-dev9
Fixed in 3.0.30, 3.2.26, 3.3.17, 3.4.6, 3.5-dev9
- >= 3.0r1, < 3.0r1-362.1441
- >= 3.2r1, < 3.2r1-378.1259
- >= 3.3r1, < 3.3r1-377.1005
Fixed in 3.0r1-362.1441, 3.2r1-378.1259, 3.3r1-377.1005
- >= 3.2.0, < 3.2.17
Fixed in 3.2.17
- >= 3.2.0, < 3.2.17-ee1
- >= 3.0, < 3.0.16-ee17
- >= 1.11, < 1.11.14-ee11
Fixed in 3.2.17-ee1, 3.0.16-ee17, 1.11.14-ee11
Mitigation
Upgrade HAProxy to 3.0.30 or 3.2.26 or 3.3.17 or 3.4.6 or 3.5-dev9 or later.
Upgrade HAProxy Enterprise Edition to 3.0r1-362.1441 or 3.2r1-378.1259 or 3.3r1-377.1005 or later.
Upgrade HAProxy Kubernetes Ingress Controller to 3.2.17 or later.
Upgrade Kubernetes Ingress Controller Enterprise to 3.2.17-ee1 or 3.0.16-ee17 or 1.11.14-ee11 or later.
References
- Vendor advisory git.haproxy.org?p=haproxy.git;a=commit;h=077906da14…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.