# CVE-2017-5931: Integer overflow in n/a

> Local privileged guest users can trigger an integer overflow in QEMU's virtio-crypto to cause a crash or execute arbitrary code on the host.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/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:** 27 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2017-5931, DEBIAN-CVE-2017-5931, GHSA-4w9r-63g7-xmfj

## What is CVE-2017-5931?

CVE-2017-5931 is a high-severity vulnerability in Qemu Qemu, published on 27 Mar 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Integer overflow in hw/virtio/virtio-crypto.c in QEMU (aka Quick Emulator) allows local guest OS privileged users to cause a denial of service (QEMU process crash) or possibly execute arbitrary code on the host via a crafted virtio-crypto request, which triggers a heap-based buffer overflow.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2017-5931?

It affects 1 product.


Products: Qemu Qemu.

## How do I fix CVE-2017-5931?

Apply the vendor's patch.

## Is CVE-2017-5931 being exploited?

There is no known exploitation of CVE-2017-5931 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-2017-5931 and fix it if it is affected.

What it is: CVE-2017-5931 is a high-severity vulnerability in Qemu Qemu, published on 27 Mar 2017. 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-2017-5931 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-2017-5931/ (Markdown: https://insights.sbomify.com/CVE-2017-5931/index.md)
```

## Sources

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

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