# CVE-2020-13791: Memory corruption in n/a

> Guest OS users can trigger out-of-bounds access in QEMU's PCI configuration space, potentially leading to code execution or denial of service.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **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:** Yes
- **Published:** 4 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-13791, GHSA-9j9x-v7hw-3v8f, UBUNTU-CVE-2020-13791

## What is CVE-2020-13791?

CVE-2020-13791 is a medium-severity memory corruption vulnerability in Qemu Qemu, published on 4 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

hw/pci/pci.c in QEMU 4.2.0 allows guest OS users to trigger an out-of-bounds access by providing an address near the end of the PCI configuration space.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2020-13791?

It affects 1 product.


Products: Qemu Qemu.

## How do I fix CVE-2020-13791?

Apply the vendor's patch.

## Is CVE-2020-13791 being exploited?

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

## Other vulnerabilities in Qemu Qemu

- [CVE-2022-36648](https://insights.sbomify.com/CVE-2022-36648/): Null dereference in n/a (critical 10.0)
- [CVE-2015-8556](https://insights.sbomify.com/CVE-2015-8556/): Race condition in n/a (critical 10.0)
- [CVE-2009-3616](https://insights.sbomify.com/CVE-2009-3616/): Use after free in n/a (critical 9.9)
- [CVE-2019-12928](https://insights.sbomify.com/CVE-2019-12928/): Command injection in n/a (critical 9.8)
- [CVE-2019-12929](https://insights.sbomify.com/CVE-2019-12929/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-13791 and fix it if it is affected.

What it is: CVE-2020-13791 is a medium-severity memory corruption vulnerability in Qemu Qemu, published on 4 Jun 2020. 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-2020-13791 in the wild and no public exploit code.

Affected product: Qemu Qemu. 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-2020-13791/ (Markdown: https://insights.sbomify.com/CVE-2020-13791/index.md)
```

## Sources

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

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