HAProxy 3 before 3.4.6 allows a remote unauthenticated attacker to cause a denial of service (persistent worker-thread CPU exhaustion) via a
- 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.0.30, 3.2.26, 3.3.17, 3.4.6, 3.5-dev9, and 7 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 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.
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.0.0 · fixed in 3.0.30; 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.0r1 · fixed in 3.0r1-362.1441; From 3.2r1 · fixed in 3.2r1-378.1259; From 3.3r1 · fixed in 3.3r1-377.1005
- HAProxy Technologies HAProxy Kubernetes Ingress Controller
From 3.2.0 · fixed in 3.2.17
- HAProxy Technologies 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