# OSV-2020-2101: Heap-buffer-overflow in lduw_he_p

> A heap buffer overflow in QEMU's memory access functions allows attackers to potentially execute code or cause a denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Oct 2020

## What is OSV-2020-2101?

OSV-2020-2101 is a memory corruption vulnerability in qemu, published on 29 Oct 2020. 

### Official description

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26691

```
Crash type: Heap-buffer-overflow READ 2
Crash state:
lduw_he_p
ldn_he_p
flatview_write_continue
```

## Which versions are affected by OSV-2020-2101?

1 open source package ship an affected version, including qemu.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `qemu` | OSS-Fuzz | All versions | None |

## How do I fix OSV-2020-2101?

No fix has been published for OSV-2020-2101 yet. Limit exposure of the affected software until one is available.

## Is OSV-2020-2101 being exploited?

There is no known exploitation of OSV-2020-2101 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for OSV-2020-2101 and fix it if it is affected.

What it is: OSV-2020-2101 is a memory corruption vulnerability in qemu, published on 29 Oct 2020. 
Exploitation: There is no known exploitation of OSV-2020-2101 in the wild and no public exploit code.

Affected packages and fixed versions:
- qemu (OSS-Fuzz): affected all versions; no fix listed

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/OSV-2020-2101/ (Markdown: https://insights.sbomify.com/OSV-2020-2101/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/OSV-2020-2101

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