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.
The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Haproxy | Haproxy | * | 2.0.32 (including) |
| Haproxy | Haproxy | 2.2.0 (including) | 2.2.30 (including) |
| Haproxy | Haproxy | 2.4.0 (including) | 2.4.23 (including) |
| Haproxy | Haproxy | 2.5.0 (including) | 2.6.15 (excluding) |
| Haproxy | Haproxy | 2.7.0 (including) | 2.7.10 (excluding) |
| Haproxy | Haproxy | 2.8.0 (including) | 2.8.2 (excluding) |
| Red Hat Enterprise Linux 9 | RedHat | haproxy-0:2.4.22-3.el9_3 | * |
| Red Hat Enterprise Linux 9.2 Extended Update Support | RedHat | haproxy-0:2.4.17-6.el9_2.2 | * |
| Red Hat OpenShift Container Platform 4.11 | RedHat | haproxy-0:2.2.24-4.rhaos4.11.el8 | * |
| Red Hat OpenShift Container Platform 4.12 | RedHat | haproxy-0:2.2.24-4.rhaos4.12.el8 | * |
| Red Hat OpenShift Container Platform 4.13 | RedHat | haproxy-0:2.2.24-4.rhaos4.13.el8 | * |
| Red Hat OpenShift Container Platform 4.14 | RedHat | haproxy-0:2.6.13-2.rhaos4.14.el8 | * |
| Haproxy | Ubuntu | bionic | * |
| Haproxy | Ubuntu | devel | * |
| Haproxy | Ubuntu | focal | * |
| Haproxy | Ubuntu | jammy | * |
| Haproxy | Ubuntu | lunar | * |
| Haproxy | Ubuntu | mantic | * |
| Haproxy | Ubuntu | trusty | * |
| Haproxy | Ubuntu | upstream | * |
| Haproxy | Ubuntu | xenial | * |
HTTP requests or responses (“messages”) can be malformed or unexpected in ways that cause web servers or clients to interpret the messages in different ways than intermediary HTTP agents such as load balancers, reverse proxies, web caching proxies, application firewalls, etc. For example, an adversary may be able to add duplicate or different header fields that a client or server might interpret as one set of messages, whereas the intermediary might interpret the same sequence of bytes as a different set of messages. For example, discrepancies can arise in how to handle duplicate headers like two Transfer-encoding (TE) or two Content-length (CL), or the malicious HTTP message will have different headers for TE and CL. The inconsistent parsing and interpretation of messages can allow the adversary to “smuggle” a message to the client/server without the intermediary being aware of it. This weakness is usually the result of the usage of outdated or incompatible HTTP protocol versions in the HTTP agents.