# CVE-2020-15687: Missing authorization in n/a

> A malicious entity with root access in the Service VM can abuse PCIe hypercalls to cause a Denial of Service for assigned devices.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-24gg-6vq3-mg4f

## What is CVE-2020-15687?

CVE-2020-15687 is a high-severity missing authorization vulnerability in n/a, published on 31 Aug 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Missing access control restrictions in the Hypervisor component of the ACRN Project (v2.0 and v1.6.1) allow a malicious entity, with root access in the Service VM userspace, to abuse the PCIe assign/de-assign Hypercalls via crafted ioctls and payloads. This attack results in a corrupt state and Denial of Service (DoS) for previously assigned PCIe devices to the Service VM at runtime.

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

It affects 1 product.


Products: Linuxfoundation Acrn.

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

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

## Is CVE-2020-15687 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-15687 is a high-severity missing authorization vulnerability in n/a, published on 31 Aug 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-15687 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-2020-15687/ (Markdown: https://insights.sbomify.com/CVE-2020-15687/index.md)
```

## Sources

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

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