Heap-based Buffer Overflow Affecting rh-haproxy18-haproxy package, versions <0:1.8.4-2.el7


Severity

Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
4.94% (93rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL7-RHHAPROXY18HAPROXY-4699721
  • published1 Nov 2021
  • disclosed19 Apr 2018

Introduced: 19 Apr 2018

CVE-2018-10184  (opens in a new tab)
CWE-122  (opens in a new tab)

How to fix?

Upgrade RHEL:7 rh-haproxy18-haproxy to version 0:1.8.4-2.el7 or higher.
This issue was patched in RHSA-2018:1372.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rh-haproxy18-haproxy package and not the rh-haproxy18-haproxy package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

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.