# CVE-2019-11059: Memory corruption in n/a

> A buffer overflow in U-Boot's ext4 64-bit extension handling allows attackers to execute arbitrary code or cause denial of service.

- **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:** 10 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-11059, GHSA-4269-qr56-7rgx, UBUNTU-CVE-2019-11059

## What is CVE-2019-11059?

CVE-2019-11059 is a critical memory corruption vulnerability in n/a, published on 10 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Das U-Boot 2016.11-rc1 through 2019.04 mishandles the ext4 64-bit extension, resulting in a buffer overflow.

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

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

It affects 1 product.


Products: Denx U-Boot.

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

Upgrade to a fixed version.

## Is CVE-2019-11059 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-34835](https://insights.sbomify.com/CVE-2022-34835/): Integer overflow in n/a (critical 9.8)
- [CVE-2022-30767](https://insights.sbomify.com/CVE-2022-30767/): Memory corruption in n/a (critical 9.8)
- [CVE-2020-8432](https://insights.sbomify.com/CVE-2020-8432/): Use after free in n/a (critical 9.8)
- [CVE-2019-14192](https://insights.sbomify.com/CVE-2019-14192/): Integer overflow in n/a (critical 9.8)
- [CVE-2019-14193](https://insights.sbomify.com/CVE-2019-14193/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-11059 is a critical memory corruption vulnerability in n/a, published on 10 May 2019. 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-2019-11059 in the wild and no public exploit code.

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

## Sources

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

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