First published: Tue Aug 17 2021(Updated: )
An issue was discovered in HAProxy 2.2 before 2.2.16, 2.3 before 2.3.13, and 2.4 before 2.4.3. It does not ensure that the scheme and path portions of a URI have the expected characters. For example, the authority field (as observed on a target HTTP/2 server) might differ from what the routing rules were intended to achieve.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
debian/haproxy | 1.8.19-1+deb10u3 1.8.19-1+deb10u4 2.2.9-2+deb11u5 2.6.12-1 2.6.15-1 | |
Haproxy Haproxy | >=2.2.0<2.2.16 | |
Haproxy Haproxy | >=2.3.0<2.3.13 | |
Haproxy Haproxy | >=2.4.0<2.4.3 | |
Debian Debian Linux | =11.0 | |
Fedoraproject Fedora | =33 | |
Fedoraproject Fedora | =34 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID is CVE-2021-39240.
HAProxy versions 2.2 before 2.2.16, 2.3 before 2.3.13, and 2.4 before 2.4.3 are affected.
The severity level of CVE-2021-39240 is high with a CVSS score of 7.5.
CVE-2021-39240 allows an attacker to bypass routing rules and affect the scheme and path portions of a URI in HAProxy.
Yes, fix versions are available. Please update to HAProxy version 2.2.16, 2.3.13, or 2.4.3 or later.