# CVE-2018-6242: Memory corruption in Some NVIDIA Tegra Mobile Processors

> An attacker with physical USB access can exploit a buffer overflow in BootROM Recovery Mode to execute unverified code on affected NVIDIA Tegra processors.

- **Severity:** Medium 6.8 (`CVSS:3.0/AV:P/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 May 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-wx59-vwv8-8whg

## What is CVE-2018-6242?

CVE-2018-6242 is a medium-severity memory corruption vulnerability in Some NVIDIA Tegra Mobile Processors, published on 1 May 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Some NVIDIA Tegra mobile processors released prior to 2016 contain a buffer overflow vulnerability in BootROM Recovery Mode (RCM). An attacker with physical access to the device's USB and the ability to force the device to reboot into RCM could exploit the vulnerability to execute unverified code.

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

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

It affects 1 product.


Products: Nvidia Tegra Bootrom Rcm.

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

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

## Is CVE-2018-6242 being exploited?

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

Public exploit code:

- My first Android app: Launch Fusée Gelée payloads from stock Android (CVE-2018-6242) (github_poc): https://github.com/DavidBuchanan314/NXLoader
- Collection of "modchip" designs for launching payloads via the Tegra RCM bug (CVE-2018-6242)  (github_poc): https://github.com/reswitched/rcm-modchips
- Rust implementation of the Fusée Gelée exploit (CVE-2018-6242) for Tegra processors. (github_poc): https://github.com/austinhartzheim/fusee-gelee
- Payload injection tool for Nintendo Switch consoles vulnerable to CVE-2018-6242 ("Fusée Gelée") (github_poc): https://github.com/nikameru/nxboot
- An app that enables payload injection into a Switch console from an Android device by exploiting the CVE-2018-6242 vulnerability (github_poc): https://github.com/Resi-le/NXLoader
- Implementation of CVE-2018-6242 (AKA Fusée Gelée, AKA shofel2) (github_poc): https://github.com/Swiftloke/fusee-toy

## Fix prompt for AI coding agents

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

What it is: CVE-2018-6242 is a medium-severity memory corruption vulnerability in Some NVIDIA Tegra Mobile Processors, published on 1 May 2018. 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-2018-6242 in the wild and no public exploit code.

Affected product: Some NVIDIA Tegra Mobile Processors. 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-6242/ (Markdown: https://insights.sbomify.com/CVE-2018-6242/index.md)
```

## Sources

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

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