Vulnerabilities · 2018 · Haproxy
CVE-2018-10184
Haproxy vulnerability
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 allocated buffer where the second fragment may overflow the heap by up to 16 kB. It is very unlikely that this can be exploited for code execution given that buffers are very short lived and their addresses not realistically predictable in production, but the likelihood of an immediate crash is absolutely certain.
Affected products
Haproxy, Enterprise Linux. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Haproxy runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- access.redhat.com/errata/RHSA-2018:1372 · Third Party Advisory
- git.haproxy.org/?p=haproxy-1.8.git%3Ba=commit%3Bh=cd117685f0cff4f2f5577ef6a21eaae96ebd9f28
- git.haproxy.org/?p=haproxy.git%3Ba=commit%3Bh=3f0e1ec70173593f4c2b3681b26c04a4ed5fc588
- nvd.nist.gov/vuln/detail/CVE-2018-10184
- cve.org/CVERecord?id=CVE-2018-10184
More vulnerabilities in Haproxy products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.