HAProxy
HAProxy 3.2 before 3.4.6 allows a remote unauthenticated attacker to cause a denial of service (worker-thread CPU exhaustion) via a truncated HTTP/2 PING frame. h2c_handle_ping in src/mux_h2.c does not check for a short read, unlike the other H2 frame handlers. Because the incomplete frame cannot be processed, its data is never consumed, and the H2 multiplexer tasklet is repeatedly woken by that pending data without making progress. The CPU spins until timeout http-request closes the connection, and an attacker opening many such connections can sustain high CPU usage.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 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.2.26, 3.3.17, 3.4.6, 3.5-dev9
- >= 3.2.0r1, < 3.2r1-378.1259
- >= 3.3.0r1, < 3.3r1-377.1005
Fixed in 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.2.26 or 3.3.17 or 3.4.6 or 3.5-dev9 or later.
Upgrade HAProxy Enterprise Edition to 3.2r1-378.1259 or 3.3r1-377.1005 or later.
Upgrade 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=cec63e95f6…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.