CVE-2018-10184

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.

Link	Resource
http://git.haproxy.org/?p=haproxy-1.8.git;a=commit;h=cd117685f0cff4f2f5577ef6a21eaae96ebd9f28	Patch Vendor Advisory
http://git.haproxy.org/?p=haproxy.git;a=commit;h=3f0e1ec70173593f4c2b3681b26c04a4ed5fc588	Patch Vendor Advisory
https://access.redhat.com/errata/RHSA-2018:1372	Third Party Advisory

Configuration 1

cpe:2.3:a:haproxy:haproxy:*:*:*:*:*:*:*:* cpe:2.3:o:redhat:enterprise_linux:7.4:*:*:*:*:*:*:* cpe:2.3:o:redhat:enterprise_linux:7.0:*:*:*:*:*:*:* cpe:2.3:o:redhat:enterprise_linux:7.3:*:*:*:*:*:*:* cpe:2.3:o:redhat:enterprise_linux:7.5:*:*:*:*:*:*:*

---

Published : 2018-05-09 07:29

Updated : 2018-06-18 05:18

---

NVD link : CVE-2018-10184

Mitre link : CVE-2018-10184

No products.

CWE-119

Improper Restriction of Operations within the Bounds of a Memory Buffer