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

> Local attackers can modify NVRAM variables to trigger a pool overflow in IEIT NF5280M6 UEFI firmware, causing a system crash.

- **Severity:** High 7.7 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 29 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-jcmq-cwf3-j6c4

## What is CVE-2023-52080?

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

### Official description

IEIT NF5280M6 UEFI firmware through 8.4 has a pool overflow vulnerability, caused by improper use of the gRT->GetVariable() function. Attackers with access to local NVRAM variables can exploit this by modifying these variables on SPI Flash, resulting in memory data being tampered with. When critical data in memory data is tampered with,a crash may occur.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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


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

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

## Is CVE-2023-52080 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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