# CVE-2019-5094: Memory corruption in E2fsprogs

> A specially crafted ext4 partition triggers an out-of-bounds heap write in E2fsprogs, allowing attackers to execute arbitrary code.

- **Severity:** High 7.5 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Sep 2019
- **Updated:** 14 Oct 2026
- **Also known as:** ALPINE-CVE-2019-5094, CLEANSTART-2024-NP33069, DEBIAN-CVE-2019-5094, DLA-1935-1, DSA-4535-1, GHSA-3498-94v2-7qqw, MGASA-2019-0296, SUSE-RU-2019:2676-1, SUSE-RU-2019:2677-1, UBUNTU-CVE-2019-5094, USN-4142-1, USN-4142-2

## What is CVE-2019-5094?

CVE-2019-5094 is a high-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 24 Sep 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An exploitable code execution vulnerability exists in the quota file functionality of E2fsprogs 1.45.3. A specially crafted ext4 partition can cause an out-of-bounds write on the heap, resulting in code execution. An attacker can corrupt a partition to trigger this vulnerability.

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

## Which versions are affected by CVE-2019-5094?

It affects 6 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `e2fsprogs` | SUSE:Linux Enterprise Desktop 12 SP4 | All versions | 1.43.8-3.8.1 |
| `e2fsprogs` | SUSE:Linux Enterprise Module for Basesystem 15 | All versions | 1.43.8-4.11.1 |
| `e2fsprogs` | SUSE:Linux Enterprise Module for Basesystem 15 SP1 | All versions | 1.43.8-4.11.1 |
| `e2fsprogs` | SUSE:Linux Enterprise Server 12 SP4 | All versions | 1.43.8-3.8.1 |
| `e2fsprogs` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 1.43.8-3.8.1 |
| `e2fsprogs` | SUSE:Linux Enterprise Software Development Kit 12 SP4 | All versions | 1.43.8-3.8.1 |

Products: Canonical Ubuntu Linux, Debian Debian Linux, E2fsprogs Project E2fsprogs, Fedoraproject Fedora, Netapp Hci Management Node, Netapp Solidfire.

## How do I fix CVE-2019-5094?

Apply the vendor's patch.

## Is CVE-2019-5094 being exploited?

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

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-5094 and fix it if it is affected.

What it is: CVE-2019-5094 is a high-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 24 Sep 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-5094 in the wild and no public exploit code.

Affected product: Canonical Ubuntu 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-2019-5094/ (Markdown: https://insights.sbomify.com/CVE-2019-5094/index.md)
```

## Sources

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

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