# CVE-2022-2347: Unchecked Download size in Uboot

> A physical attacker can exploit an unchecked length field in U-Boot's DFU implementation to write beyond heap buffers, potentially executing arbitrary code.

- **Severity:** High 7.7 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 23 Sep 2022
- **Updated:** 12 May 2026
- **Also known as:** DEBIAN-CVE-2022-2347, GHSA-57ww-qgjv-3g3c, OESA-2024-2186, OESA-2024-2187, OESA-2024-2188, OESA-2024-2189, UBUNTU-CVE-2022-2347

## What is CVE-2022-2347?

CVE-2022-2347 is a high-severity memory corruption vulnerability in Uboot, published on 23 Sep 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

There exists an unchecked length field in UBoot. The U-Boot DFU implementation does not bound the length field in USB DFU download setup packets, and it does not verify that the transfer direction corresponds to the specified command. Consequently, if a physical attacker crafts a USB DFU download setup packet with a `wLength` greater than 4096 bytes, they can write beyond the heap-allocated request buffer.

Weakness: CWE-787 (Out-of-bounds Write), CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2022-2347?

It affects 1 product.


Products: Denx U-Boot.

## How do I fix CVE-2022-2347?

Apply the vendor's patch.

## Is CVE-2022-2347 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-2347 exists.

## Other vulnerabilities in Uboot

- [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-2022-2347 and fix it if it is affected.

What it is: CVE-2022-2347 is a high-severity memory corruption vulnerability in Uboot, published on 23 Sep 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-2347 exists.

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

## Sources

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

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