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.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Haproxy | Haproxy | 2.2.0 (including) | 2.2.16 (excluding) |
| Haproxy | Haproxy | 2.3.0 (including) | 2.3.13 (excluding) |
| Haproxy | Haproxy | 2.4.0 (including) | 2.4.3 (excluding) |
| Red Hat OpenShift Container Platform 4.8 | RedHat | haproxy-0:2.2.13-2.el8 | * |
| Red Hat OpenShift Container Platform 4.9 | RedHat | haproxy-0:2.2.15-2.el8 | * |
| Haproxy | Ubuntu | devel | * |
| Haproxy | Ubuntu | hirsute | * |
| Haproxy | Ubuntu | impish | * |
| Haproxy | Ubuntu | jammy | * |
| Haproxy | Ubuntu | trusty | * |
| Haproxy | Ubuntu | xenial | * |