CVE-2018-10184: Buffer Overflow
An issue was discovered in HAProxy before 1.8.8. The incoming H2 frame length was checked against the maxframesize setting instead of being checked against the bufsize. The maxframesize 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.
Other sources
HAProxy 1.8.x before version 1.8.8 is vulnerable to a heap-based buffer overflow in the muxh2.c:h2processdemux() function. A remote attacker could exploit this to overflow the heap by 16kb to cause a denial of service or other potential unspecified impact.
— Red Hat
Affected Software
Remediation
Event History
Frequently Asked Questions
What is CVE-2018-10184?
CVE-2018-10184 is a vulnerability discovered in HAProxy before version 1.8.8. The vulnerability allows for a bypass of security restrictions.
What is the severity of CVE-2018-10184?
The severity of CVE-2018-10184 is high, with a severity value of 7.5.
How does CVE-2018-10184 affect HAProxy?
CVE-2018-10184 affects HAProxy before version 1.8.8. It allows for a bypass of security restrictions related to H2 frame length checking.
How can I mitigate the impact of CVE-2018-10184?
To mitigate the impact of CVE-2018-10184, it is recommended to update HAProxy to version 1.8.8 or higher.
Where can I find more information about CVE-2018-10184?
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.