HAProxy 3.2 before 3.4.6 allows a remote unauthenticated attacker to cause a denial of service (worker-thread CPU exhaustion) via a truncate
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.2.26, 3.3.17, 3.4.6, 3.5-dev9, 3.2r1-378.1259, and 5 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- HAProxy HAProxy
From 3.2.0 · fixed in 3.2.26; From 3.3.0 · fixed in 3.3.17; From 3.4.0 · fixed in 3.4.6; From 3.5-dev · fixed in 3.5-dev9
- HAProxy HAProxy Enterprise Edition
From 3.2.0r1 · fixed in 3.2r1-378.1259; From 3.3.0r1 · fixed in 3.3r1-377.1005
- HAProxy Kubernetes Ingress Controller
From 3.2.0 · fixed in 3.2.17
- Haproxy Kubernetes Ingress Controller Enterprise
From 3.2.0 · fixed in 3.2.17-ee1; From 3.0 · fixed in 3.0.16-ee17; From 1.11 · fixed in 1.11.14-ee11