First published: Wed Mar 29 2023(Updated: )
An information leak vulnerability was discovered in HAProxy 2.1, 2.2 before 2.2.27, 2.3, 2.4 before 2.4.21, 2.5 before 2.5.11, 2.6 before 2.6.8, 2.7 before 2.7.1. There are 5 bytes left uninitialized in the connection buffer when encoding the FCGI_BEGIN_REQUEST record. Sensitive data may be disclosed to configured FastCGI backends in an unexpected way.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Haproxy Haproxy | >=2.2.0<2.2.27 | |
Haproxy Haproxy | >=2.4.0<=2.4.21 | |
Haproxy Haproxy | >=2.5.0<=2.5.11 | |
Haproxy Haproxy | >=2.6.0<=2.6.8 | |
Haproxy Haproxy | =2.1.0 | |
Haproxy Haproxy | =2.3.0 | |
Haproxy Haproxy | =2.7.0 | |
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 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID for this information leak vulnerability is CVE-2023-0836.
The severity of CVE-2023-0836 is high with a severity value of 7.5.
The affected software versions of CVE-2023-0836 include HAProxy 2.1, 2.2 (up to 2.2.27), 2.3, 2.4 (up to 2.4.21), 2.5 (up to 2.5.11), 2.6 (up to 2.6.8), and 2.7 (up to 2.7.1).
An attacker can exploit this vulnerability by sending specially crafted requests to the vulnerable HAProxy server which could lead to an information leak.
To fix CVE-2023-0836, it is recommended to upgrade to the patched versions of HAProxy, such as 2.2.27, 2.4.21, 2.5.11, 2.6.8, or 2.7.1, depending on the version you are using.