Buffer overflow in Haproxy
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.
Vulnerability class: Buffer Overflow
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
EPSS exploit prediction
EPSS 0.081, 94.9th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Haproxy
- Red Hat Enterprise Linux — versions 7.0, 7.3, 7.4
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (ARPSyndicate/cve-scores). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- git.haproxy.org/
- RHSA-2018:1372 (vendor-advisory, Third Party Advisory)
- git.haproxy.org/