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

> A heap-based buffer overflow in Keepalived allows attackers to cause denial of service or potentially execute arbitrary code via crafted HTTP status codes.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 8 Nov 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-19115, DLA-1589-1, GHSA-q8cg-hf8f-hgf3, RHSA-2019:0022, RHSA-2019:1792, RHSA-2019:1945, UBUNTU-CVE-2018-19115, USN-3995-1, USN-3995-2

## What is CVE-2018-19115?

CVE-2018-19115 is a critical memory corruption vulnerability in Debian Debian Linux, published on 8 Nov 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

keepalived before 2.0.7 has a heap-based buffer overflow when parsing HTTP status codes resulting in DoS or possibly unspecified other impact, because extract_status_code in lib/html.c has no validation of the status code and instead writes an unlimited amount of data to the heap.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 7 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `keepalived` | Red Hat:enterprise_linux:7::server | All versions | 0:1.3.5-8.el7_6 |
| `keepalived-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:1.3.5-8.el7_6 |
| `keepalived` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.3.5-8.el7_6 |
| `keepalived-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.3.5-8.el7_6 |
| `keepalived` | Red Hat:rhel_eus:7.4::server | All versions | 0:1.3.5-1.el7_4.1 |
| `keepalived-debuginfo` | Red Hat:rhel_eus:7.4::server | All versions | 0:1.3.5-1.el7_4.1 |
| `keepalived` | Red Hat:rhel_eus:7.5::server | All versions | 0:1.3.5-7.el7_5.2 |
| `keepalived-debuginfo` | Red Hat:rhel_eus:7.5::server | All versions | 0:1.3.5-7.el7_5.2 |

Products: Debian Debian Linux, Keepalived Keepalived, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Eus, Redhat Enterprise Linux Server Tus, Redhat Enterprise Linux Workstation.

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

Upgrade to a fixed version.

## Is CVE-2018-19115 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-19115 is a critical memory corruption vulnerability in Debian Debian Linux, published on 8 Nov 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-19115 in the wild and no public exploit code.

Affected product: Debian Debian 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-19115/ (Markdown: https://insights.sbomify.com/CVE-2018-19115/index.md)
```

## Sources

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

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