# CVE-2018-10184: Memory corruption in n/a

> A heap overflow in HAProxy's HTTP/2 frame handling allows remote attackers to cause a denial of service via crafted frames.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** CVE-2018-1119, DEBIAN-CVE-2018-10184, GHSA-v27h-hh5q-3p4q, RHBA-2018:1566, RHSA-2018:1372

## What is CVE-2018-10184?

CVE-2018-10184 is a high-severity memory corruption vulnerability in Redhat Enterprise Linux, published on 9 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2018-10184?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `haproxy` | Red Hat:openshift:3.9::el7 | All versions | 0:1.8.8-1.el7 |
| `haproxy-debuginfo` | Red Hat:openshift:3.9::el7 | All versions | 0:1.8.8-1.el7 |
| `haproxy18` | Red Hat:openshift:3.9::el7 | All versions | 0:1.8.8-1.el7 |
| `rh-haproxy18-haproxy` | Red Hat:rhel_software_collections:3::el7 | All versions | 0:1.8.4-2.el7 |
| `rh-haproxy18-haproxy-debuginfo` | Red Hat:rhel_software_collections:3::el7 | All versions | 0:1.8.4-2.el7 |
| `rh-haproxy18-haproxy-syspaths` | Red Hat:rhel_software_collections:3::el7 | All versions | 0:1.8.4-2.el7 |

Products: Haproxy Haproxy, Redhat Enterprise Linux.

## How do I fix CVE-2018-10184?

Upgrade to a fixed version.

## Is CVE-2018-10184 being exploited?

There is no known exploitation of CVE-2018-10184 in the wild and no public exploit code.

## Other vulnerabilities in Redhat Enterprise Linux

- [CVE-2026-55203](https://insights.sbomify.com/CVE-2026-55203/): HAProxy - Integer Overflow in FCGI Demux Record Length Field (critical 9.0)
- [CVE-2026-55204](https://insights.sbomify.com/CVE-2026-55204/): HAProxy - NULL Pointer Dereference in hpack_dht_insert Function (high 8.7)
- [CVE-2023-45539](https://insights.sbomify.com/CVE-2023-45539/): Information disclosure in n/a (high 8.2)
- [CVE-2024-45506](https://insights.sbomify.com/CVE-2024-45506/): Denial of service in n/a (high 7.5)
- [CVE-2023-0836](https://insights.sbomify.com/CVE-2023-0836/): Information disclosure in HAProxy (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-10184 and fix it if it is affected.

What it is: CVE-2018-10184 is a high-severity memory corruption vulnerability in Redhat Enterprise Linux, published on 9 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-10184 in the wild and no public exploit code.

Affected product: Redhat Enterprise Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-10184/ (Markdown: https://insights.sbomify.com/CVE-2018-10184/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-10184
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-10184
- OSV: https://osv.dev/vulnerability/CVE-2018-10184

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-10184/
Summaries are generated and may contain mistakes; the official description above is the record.