# CVE-2023-39902: Memory corruption in n/a

> Attackers can overwrite SPL memory via crafted FIT images to execute unauthenticated code and escalate privileges on NXP i.MX 8M processors.

- **Severity:** High 7.0 (`CVSS:3.1/AC:H/AV:L/A:H/C:H/I:H/PR:L/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Oct 2023
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-cj3f-w95j-x9xv

## What is CVE-2023-39902?

CVE-2023-39902 is a high-severity memory corruption vulnerability in n/a, published on 17 Oct 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A software vulnerability has been identified in the U-Boot Secondary Program Loader (SPL) before 2023.07 on select NXP i.MX 8M family processors. Under certain conditions, a crafted Flattened Image Tree (FIT) format structure can be used to overwrite SPL memory, allowing unauthenticated software to execute on the target, leading to privilege escalation. This affects i.MX 8M, i.MX 8M Mini, i.MX 8M Nano, and i.MX 8M Plus.

Weakness: CWE-281 (Improper Preservation of Permissions)

## Which versions are affected by CVE-2023-39902?

It affects 1 product.


Products: Nxp Uboot Secondary Program Loader.

## How do I fix CVE-2023-39902?

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

## Is CVE-2023-39902 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-39902 and fix it if it is affected.

What it is: CVE-2023-39902 is a high-severity memory corruption vulnerability in n/a, published on 17 Oct 2023. 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-2023-39902 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-2023-39902/ (Markdown: https://insights.sbomify.com/CVE-2023-39902/index.md)
```

## Sources

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

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