CVE-2018-10184: n/a vulnerability

CVE-2018-10184: An issue was discovered in HAProxy before 1.8.8.

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.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 5, 2024, 07:32 UTC (UTC+00:00)

Security readout for executives and security teams

CVE-2018-10184 can let a remote client crash HAProxy versions before 1.8.8 when HTTP/2 frame handling is exposed. The source states code execution is very unlikely, but an immediate crash is expected, making this primarily an availability risk. Exposure is most likely on HAProxy deployments before 1.8.8 that accept HTTP/2 traffic, especially internet-facing reverse proxies and load balancers. The provided affected-product metadata is incomplete, so inventory should rely on deployed HAProxy versions and vendor packages. Treat this as urgent for exposed load balancers because a crash can interrupt customer traffic. It is less severe than a proven remote code execution issue, but availability impact can still be business-critical. Mitigation focus: Upgrade HAProxy to 1.8.8 or a vendor-supported fixed release.; Apply Red Hat advisory packages where Red Hat builds are in use.; Prioritize internet-facing HAProxy instances that accept HTTP/2 traffic..

Prepared: Jun 7, 2026, 13:40 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup

cve · low confidence lookup

CVE-2018-10184 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: May 9, 2018, 07:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
RHSA-2018:1372CVE reference · vendor-advisory, x_refsource_REDHAT

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.