# CVE-2019-5680: Code injection in NVIDIA Jetson TX1

> Attackers can execute arbitrary code or escalate privileges by exploiting missing load address validation in the NVIDIA Jetson TX1 bootloader.

- **Severity:** Medium 6.7 (`CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/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:** No
- **Published:** 19 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-xq52-whfh-4w3m

## What is CVE-2019-5680?

CVE-2019-5680 is a medium-severity code injection vulnerability in NVIDIA Jetson TX1, published on 19 Jul 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In NVIDIA Jetson TX1 L4T R32 version branch prior to R32.2, Tegra bootloader contains a vulnerability in nvtboot in which the nvtboot-cpu image is loaded without the load address first being validated, which may lead to code execution, denial of service, or escalation of privileges.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Nvidia Jetson Tx1 Firmware.

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

No fix has been published for CVE-2019-5680 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-5680 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-5680 is a medium-severity code injection vulnerability in NVIDIA Jetson TX1, published on 19 Jul 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-5680 in the wild and no public exploit code.

Affected product: NVIDIA Jetson TX1. 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-5680/ (Markdown: https://insights.sbomify.com/CVE-2019-5680/index.md)
```

## Sources

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

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