CVE-2021-39240
published 2021-08-17CVE-2021-39240: 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…
PriorityP341high7.5CVSS 3.1
AVNACLPRNUINSUCHINAN
EPSS
2.32%
81.5th percentile
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.
Affected
11 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | debian_linux | — | — |
| debian | haproxy | < haproxy 2.2.16-1 (bookworm) | haproxy 2.2.16-1 (bookworm) |
| fedoraproject | fedora | — | — |
| fedoraproject | fedora | — | — |
| haproxy | haproxy | >= 0 < 2.2.9-2+deb11u1 | 2.2.9-2+deb11u1 |
| haproxy | haproxy | >= 0 < 2.2.16-1 | 2.2.16-1 |
| haproxy | haproxy | >= 0 < 2.2.16-1 | 2.2.16-1 |
| haproxy | haproxy | >= 0 < 2.2.16-1 | 2.2.16-1 |
| haproxy | haproxy | >= 2.2.0 < 2.2.16 | 2.2.16 |
| haproxy | haproxy | >= 2.3.0 < 2.3.13 | 2.3.13 |
| haproxy | haproxy | >= 2.4.0 < 2.4.3 | 2.4.3 |
CVSS provenance
nvdv3.17.5HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:P/I:N/A:N
osv7.5HIGH
vendor_debian7.5HIGH
vendor_redhat7.5HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-88gq-424p-x3xc: An issue was discovered in HAProxy 2
ghsa_unreviewed·2022-05-24
CVE-2021-39240 [HIGH] GHSA-88gq-424p-x3xc: An issue was discovered in HAProxy 2
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.
OSV
CVE-2021-39240: An issue was discovered in HAProxy 2
osv·2021-08-17·CVSS 7.5
CVE-2021-39240 [HIGH] CVE-2021-39240: An issue was discovered in HAProxy 2
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.
Red Hat
haproxy: does not ensure that the scheme and path portions of a URI have the expected characters
vendor_redhat·2021-08-17·CVSS 7.5
CVE-2021-39240 [HIGH] CWE-20 haproxy: does not ensure that the scheme and path portions of a URI have the expected characters
haproxy: does not ensure that the scheme and path portions of a URI have the expected characters
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.
A flaw was found in haproxy. An input validation flaw when processing HTTP/2 requests causes haproxy to not ensure that the scheme and path portions of a URI have the expected characters. This may cause specially crafted input to bypass implemented security restrictions. The highest threat from this vulnerability is confidentiality.
Package: haproxy (Red Hat Enterprise L
Debian
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...
vendor_debian·2021·CVSS 7.5
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 2.2.16-1)
bullseye: resolved (fixed in 2.2.9-2+deb11u1)
forky: resolved (fixed in 2.2.16-1)
sid: resolved (fixed in 2.2.16-1)
trixie: resolved (fixed in 2.2.16-1)
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://git.haproxy.org/?p=haproxy.git%3Ba=commit%3Bh=4b8852c70d8c4b7e225e24eb58258a15eb54c26ehttps://git.haproxy.org/?p=haproxy.git%3Ba=commit%3Bh=a495e0d94876c9d39763db319f609351907a31e8https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4ALECUZDIMT5FYGP6V6PVSI4BKVZTZWN/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/RPNY4WZIQUAUOCLIMUPC37AQWNXTWIQM/https://www.debian.org/security/2021/dsa-4960https://www.mail-archive.com/haproxy%40formilux.org/msg41041.htmlhttps://git.haproxy.org/?p=haproxy.git%3Ba=commit%3Bh=4b8852c70d8c4b7e225e24eb58258a15eb54c26ehttps://git.haproxy.org/?p=haproxy.git%3Ba=commit%3Bh=a495e0d94876c9d39763db319f609351907a31e8https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4ALECUZDIMT5FYGP6V6PVSI4BKVZTZWN/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/RPNY4WZIQUAUOCLIMUPC37AQWNXTWIQM/https://www.debian.org/security/2021/dsa-4960https://www.mail-archive.com/haproxy%40formilux.org/msg41041.html
2021-08-17
Published