Debian Haproxy vulnerabilities

CVE-2023-44487 [HIGH] CVE-2023-44487: dnsdist - The HTTP/2 protocol allows a denial of service (server resource consumption) bec... The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023. Scope: local bookworm: open bullseye: open forky: resolved (fixed in 1.8.2-2) sid: resolved (fixed in 1.8.2-2) trixie: resolved (fixed in 1.8.2-2)

CVE-2024-45506 [HIGH] CVE-2024-45506: haproxy - HAProxy 2.9.x before 2.9.10, 3.0.x before 3.0.4, and 3.1.x through 3.1-dev6 allo... HAProxy 2.9.x before 2.9.10, 3.0.x before 3.0.4, and 3.1.x through 3.1-dev6 allows a remote denial of service for HTTP/2 zero-copy forwarding (h2_send loop) under a certain set of conditions, as exploited in the wild in 2024. Scope: local bookworm: resolved bullseye: resolved forky: resolved (fixed in 2.9.10-1) sid: resolved (fixed in 2.9.10-1) trixie: resolved (fix

CVE-2020-11100 [HIGH] CVE-2020-11100: haproxy - In hpack_dht_insert in hpack-tbl.c in the HPACK decoder in HAProxy 1.8 through 2... In hpack_dht_insert in hpack-tbl.c in the HPACK decoder in HAProxy 1.8 through 2.x before 2.1.4, a remote attacker can write arbitrary bytes around a certain location on the heap via a crafted HTTP/2 request, possibly causing remote code execution. Scope: local bookworm: resolved (fixed in 2.0.13-2) bullseye: resolved (fixed in 2.0.13-2) forky: resolved (fixed in 2.

CVE-2021-40346 [HIGH] CVE-2021-40346: haproxy - An integer overflow exists in HAProxy 2.0 through 2.5 in htx_add_header that can... An integer overflow exists in HAProxy 2.0 through 2.5 in htx_add_header that can be exploited to perform an HTTP request smuggling attack, allowing an attacker to bypass all configured http-request HAProxy ACLs and possibly other ACLs. Scope: local bookworm: resolved (fixed in 2.2.16-3) bullseye: resolved (fixed in 2.2.9-2+deb11u2) forky: resolved (fixed in 2.2.16-3

CVE-2023-25725 [CRITICAL] CVE-2023-25725: haproxy - HAProxy before 2.7.3 may allow a bypass of access control because HTTP/1 headers... HAProxy before 2.7.3 may allow a bypass of access control because HTTP/1 headers are inadvertently lost in some situations, aka "request smuggling." The HTTP header parsers in HAProxy may accept empty header field names, which could be used to truncate the list of HTTP headers and thus make some headers disappear after being parsed and processed for HTTP/1.0 and

CVE-2016-5360 [HIGH] CVE-2016-5360: haproxy - HAproxy 1.6.x before 1.6.6, when a deny comes from a reqdeny rule, allows remote... HAproxy 1.6.x before 1.6.6, when a deny comes from a reqdeny rule, allows remote attackers to cause a denial of service (uninitialized memory access and crash) or possibly have unspecified other impact via unknown vectors. Scope: local bookworm: resolved (fixed in 1.6.5-2) bullseye: resolved (fixed in 1.6.5-2) forky: resolved (fixed in 1.6.5-2) sid: resolved (fixed in

CVE-2022-0711 [HIGH] CVE-2022-0711: haproxy - A flaw was found in the way HAProxy processed HTTP responses containing the "Set... A flaw was found in the way HAProxy processed HTTP responses containing the "Set-Cookie2" header. This flaw could allow an attacker to send crafted HTTP response packets which lead to an infinite loop, eventually resulting in a denial of service condition. The highest threat from this vulnerability is availability. Scope: local bookworm: resolved (fixed in 2.4.13-1) b

CVE-2025-8671 [HIGH] CVE-2025-8671: h2o - A mismatch caused by client-triggered server-sent stream resets between HTTP/2 s... A mismatch caused by client-triggered server-sent stream resets between HTTP/2 specifications and the internal architectures of some HTTP/2 implementations may result in excessive server resource consumption leading to denial-of-service (DoS). By opening streams and then rapidly triggering the server to reset them—using malformed frames or flow control errors—an attacker

CVE-2019-18277 [HIGH] CVE-2019-18277: haproxy - A flaw was found in HAProxy before 2.0.6. In legacy mode, messages featuring a t... 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 parse

CVE-2019-19330 [CRITICAL] CVE-2019-19330: haproxy - The HTTP/2 implementation in HAProxy before 2.0.10 mishandles headers, as demons... The HTTP/2 implementation in HAProxy before 2.0.10 mishandles headers, as demonstrated by carriage return (CR, ASCII 0xd), line feed (LF, ASCII 0xa), and the zero character (NUL, ASCII 0x0), aka Intermediary Encapsulation Attacks. Scope: local bookworm: resolved (fixed in 2.0.10-1) bullseye: resolved (fixed in 2.0.10-1) forky: resolved (fixed in 2.0.10-1) sid: r

CVE-2018-10184 [HIGH] CVE-2018-10184: haproxy - An issue was discovered in HAProxy before 1.8.8. The incoming H2 frame length wa... An issue was discovered in HAProxy before 1.8.8. The incoming H2 frame length was checked against the max_frame_size setting instead of being checked against the bufsize. The max_frame_size only applies to outgoing traffic and not to incoming, so if a large enough frame size is advertised in the SETTINGS frame, a wrapped frame will be defragmented into a temporary a

CVE-2018-20102 [HIGH] CVE-2018-20102: haproxy - An out-of-bounds read in dns_validate_dns_response in dns.c was discovered in HA... An out-of-bounds read in dns_validate_dns_response in dns.c was discovered in HAProxy through 1.8.14. Due to a missing check when validating DNS responses, remote attackers might be able read the 16 bytes corresponding to an AAAA record from the non-initialized part of the buffer, possibly accessing anything that was left on the stack, or even past the end of the 81

CVE-2023-45539 [HIGH] CVE-2023-45539: haproxy - HAProxy before 2.8.2 accepts # as part of the URI component, which might allow r... HAProxy before 2.8.2 accepts # as part of the URI component, which might allow remote attackers to obtain sensitive information or have unspecified other impact upon misinterpretation of a path_end rule, such as routing index.html#.png to a static server. Scope: local bookworm: resolved (fixed in 2.6.12-1+deb12u1) bullseye: resolved (fixed in 2.2.9-2+deb11u6) forky:

CVE-2021-39240 [HIGH] CVE-2021-39240: haproxy - An issue was discovered in HAProxy 2.2 before 2.2.16, 2.3 before 2.3.13, and 2.4... 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. Scope: local bookworm: resolved (fixed in

CVE-2023-0836 [HIGH] CVE-2023-0836: haproxy - An information leak vulnerability was discovered in HAProxy 2.1, 2.2 before 2.2.... 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. Scope: local bo

CVE-2018-20103 [HIGH] CVE-2018-20103: haproxy - An issue was discovered in dns.c in HAProxy through 1.8.14. In the case of a com... An issue was discovered in dns.c in HAProxy through 1.8.14. In the case of a compressed pointer, a crafted packet can trigger infinite recursion by making the pointer point to itself, or create a long chain of valid pointers resulting in stack exhaustion. Scope: local bookworm: resolved (fixed in 1.8.15-1) bullseye: resolved (fixed in 1.8.15-1) forky: resolved (fixe

CVE-2023-40225 [HIGH] CVE-2023-40225: haproxy - HAProxy through 2.0.32, 2.1.x and 2.2.x through 2.2.30, 2.3.x and 2.4.x through ... HAProxy through 2.0.32, 2.1.x and 2.2.x through 2.2.30, 2.3.x and 2.4.x through 2.4.23, 2.5.x and 2.6.x before 2.6.15, 2.7.x before 2.7.10, and 2.8.x before 2.8.2 forwards empty Content-Length headers, violating RFC 9110 section 8.6. In uncommon cases, an HTTP/1 server behind HAProxy may interpret the payload as an extra request. Scope: local bookworm: resolved (fix

CVE-2025-11230 [HIGH] CVE-2025-11230: haproxy - Inefficient algorithm complexity in mjson in HAProxy allows remote attackers to ... Inefficient algorithm complexity in mjson in HAProxy allows remote attackers to cause a denial of service via specially crafted JSON requests. Scope: local bookworm: resolved (fixed in 2.6.12-1+deb12u3) bullseye: resolved forky: resolved (fixed in 3.2.5-2) sid: resolved (fixed in 3.2.5-2) trixie: resolved (fixed in 3.0.11-1+deb13u1)

CVE-2023-25950 [HIGH] CVE-2023-25950: haproxy - HTTP request/response smuggling vulnerability in HAProxy version 2.7.0, and 2.6.... HTTP request/response smuggling vulnerability in HAProxy version 2.7.0, and 2.6.1 to 2.6.7 allows a remote attacker to alter a legitimate user's request. As a result, the attacker may obtain sensitive information or cause a denial-of-service (DoS) condition. Scope: local bookworm: resolved (fixed in 2.6.8-1) bullseye: resolved forky: resolved (fixed in 2.6.8-1) sid:

CVE-2021-39242 [HIGH] CVE-2021-39242: haproxy - An issue was discovered in HAProxy 2.2 before 2.2.16, 2.3 before 2.3.13, and 2.4... 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 can lead to a situation with an attacker-controlled HTTP Host header, because a mismatch between Host and authority is mishandled. Scope: local bookworm: resolved (fixed in 2.2.16-1) bullseye: resolved (fixed in 2.2.9-2+deb11u1) forky: resolved (fixed in 2.2.16-1) sid: