# CVE-2017-2633: Memory corruption in Qemu:

> A guest user can crash the QEMU process via an out-of-bounds memory access in the VNC display driver, causing denial of service.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:A/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:L`)
- **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 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-2633, GHSA-c46f-47cq-c2fg, UBUNTU-CVE-2017-2633

## What is CVE-2017-2633?

CVE-2017-2633 is a medium-severity memory corruption vulnerability in Qemu Qemu, published on 27 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An out-of-bounds memory access issue was found in Quick Emulator (QEMU) before 1.7.2 in the VNC display driver. This flaw could occur while refreshing the VNC display surface area in the 'vnc_refresh_server_surface'. A user inside a guest could use this flaw to crash the QEMU process.

Weakness: CWE-787 (Out-of-bounds Write), CWE-125 (Out-of-bounds Read), CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 6 products.


Products: Qemu Qemu, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Eus, Redhat Enterprise Linux Workstation.

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

Upgrade to a fixed version.

## Is CVE-2017-2633 being exploited?

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

What it is: CVE-2017-2633 is a medium-severity memory corruption vulnerability in Qemu Qemu, published on 27 Jul 2018. 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-2633 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-2633/ (Markdown: https://insights.sbomify.com/CVE-2017-2633/index.md)
```

## Sources

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

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