CVE-2018-10184

haproxy: Heap buffer overflow in mux_h2.c:h2_process_demux() can allow attackers to cause a denial of service

Published May 9, 2018 CVSS 3.0 · 7.5 High EPSS 8.1% KEV · Not listed
Description
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History

No history.

Weaknesses

Sources

Status
PUBLISHED
Assigner
mitre
Published
Updated
Aug 5, 2024, 7:32 AM
Reserved
Apr 17, 2018, 12:00 AM
Status
Modified
Published
May 9, 2018, 7:29 AM
Modified
Jun 17, 2026, 1:33 AM
Severity
Important
Public date
Apr 19, 2018, 12:00 AM