First published: Thu Apr 19 2018(Updated: )
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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/haproxy | <1.8.8 | 1.8.8 |
Haproxy Haproxy | <1.8.8 | |
Redhat Enterprise Linux | =7.0 | |
Redhat Enterprise Linux | =7.3 | |
Redhat Enterprise Linux | =7.4 | |
Redhat Enterprise Linux | =7.5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2018-10184 is a vulnerability discovered in HAProxy before version 1.8.8. The vulnerability allows for a bypass of security restrictions.
The severity of CVE-2018-10184 is high, with a severity value of 7.5.
CVE-2018-10184 affects HAProxy before version 1.8.8. It allows for a bypass of security restrictions related to H2 frame length checking.
To mitigate the impact of CVE-2018-10184, it is recommended to update HAProxy to version 1.8.8 or higher.
More information about CVE-2018-10184 can be found in the references provided: http://git.haproxy.org/?p=haproxy-1.8.git;a=commit;h=cd117685f0cff4f2f5577ef6a21eaae96ebd9f28, http://git.haproxy.org/?p=haproxy.git;a=commit;h=3f0e1ec70173593f4c2b3681b26c04a4ed5fc588, and https://access.redhat.com/errata/RHSA-2018:1372.