CVE-2021-39240: Haproxy vulnerability
Vendor fix available · Affected: Haproxy · Exploitation: possible (1 to 10%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 82% of scored CVEs
Not scored yet. The CVE record carries no CVSS score.
DescriptionCVE.org
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.
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Possible (1 to 10%). EPSS between 1% and 10%.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- Haproxy
- Published
- August 2021
CoverageNo articles yet
No CyberSIXT article names CVE-2021-39240 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.
References
- NVD entrynvd.nist.gov
- CVE recordcve.org
- Vendor advisorydebian.org
- Vendor advisorylists.fedoraproject.org
- Vendor advisorylists.fedoraproject.org
- mail-archive.com/haproxy%40formilux.org/msg41041.htmlmail-archive.com
- git.haproxy.org/?p=haproxy.git%3Ba=commit%3Bh=a495e0d94876c9d397git.haproxy.org
- git.haproxy.org/?p=haproxy.git%3Ba=commit%3Bh=4b8852c70d8c4b7e22git.haproxy.org