First published: Tue Oct 08 2019(Updated: )
A flaw was found in HAProxy before 2.0.6. In legacy mode, messages featuring a transfer-encoding header missing the "chunked" value were not being correctly rejected. The impact was limited but if combined with the "http-reuse always" setting, it could be used to help construct an HTTP request smuggling attack against a vulnerable component employing a lenient parser that would ignore the content-length header as soon as it saw a transfer-encoding one (even if not entirely valid according to the specification).
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Haproxy Haproxy | <2.0.6 | |
redhat/haproxy | <2.0.6 | 2.0.6 |
redhat/haproxy | <1.8.22 | 1.8.22 |
ubuntu/haproxy | <1.8.8-1ubuntu0.7 | 1.8.8-1ubuntu0.7 |
ubuntu/haproxy | <1.8.19-1ubuntu1.2 | 1.8.19-1ubuntu1.2 |
ubuntu/haproxy | <2.0.5-1ubuntu0.2 | 2.0.5-1ubuntu0.2 |
ubuntu/haproxy | <2.0.6-1 | 2.0.6-1 |
ubuntu/haproxy | <1.6.3-1ubuntu0.3 | 1.6.3-1ubuntu0.3 |
debian/haproxy | 2.2.9-2+deb11u6 2.6.12-1+deb12u1 2.9.10-1 |
https://git.haproxy.org/?p=haproxy-2.0.git;a=commit;h=196a7df44d8129d1adc795da020b722614d6a581
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID for this flaw in HAProxy is CVE-2019-18277.
The severity level of CVE-2019-18277 is high with a severity value of 7.5.
The impact of CVE-2019-18277 is limited but can be used to help construct an HTTP request smuggling attack.
HAProxy versions before 2.0.6 and versions before 1.8.22 are affected by this vulnerability.
To fix CVE-2019-18277, it is recommended to update HAProxy to version 2.0.6 or version 1.8.22.