# CVE-2017-2620: Memory corruption in Qemu: > A privileged guest user can trigger an out-of-bounds access in QEMU's Cirrus VGA emulator to crash the process or execute arbitrary code on the host. - **Severity:** Medium 5.5 (`CVSS:3.0/AV:A/AC:H/PR:L/UI:N/S:C/C:L/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:** ALPINE-CVE-2017-2620, DEBIAN-CVE-2017-2620, GHSA-v6gr-ph59-9hqm, RHSA-2017:0351, RHSA-2017:0352, UBUNTU-CVE-2017-2620 ## What is CVE-2017-2620? CVE-2017-2620 is a medium-severity memory corruption vulnerability in Citrix Xenserver, 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 Quick emulator (QEMU) before 2.8 built with the Cirrus CLGD 54xx VGA Emulator support is vulnerable to an out-of-bounds access issue. The issue could occur while copying VGA data in cirrus_bitblt_cputovideo. A privileged user inside guest could use this flaw to crash the QEMU process OR potentially execute arbitrary code on host with privileges of the QEMU process. Weakness: CWE-125 (Out-of-bounds Read), CWE-787 (Out-of-bounds Write) ## Which versions are affected by CVE-2017-2620? It affects 10 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `qemu-guest-agent` | Red Hat:enterprise_linux:6::client | All versions | 2:0.12.1.2-2.491.el6_8.7 | | `qemu-img` | Red Hat:enterprise_linux:6::client | All versions | 2:0.12.1.2-2.491.el6_8.7 | | `qemu-kvm` | Red Hat:enterprise_linux:6::client | All versions | 2:0.12.1.2-2.491.el6_8.7 | | `qemu-kvm-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 2:0.12.1.2-2.491.el6_8.7 | | `qemu-kvm-tools` | Red Hat:enterprise_linux:6::client | All versions | 2:0.12.1.2-2.491.el6_8.7 | | `qemu-guest-agent` | Red Hat:enterprise_linux:6::computenode | All versions | 2:0.12.1.2-2.491.el6_8.7 | | `qemu-img` | Red Hat:enterprise_linux:6::computenode | All versions | 2:0.12.1.2-2.491.el6_8.7 | | `qemu-kvm` | Red Hat:enterprise_linux:6::computenode | All versions | 2:0.12.1.2-2.491.el6_8.7 | | `qemu-kvm-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 2:0.12.1.2-2.491.el6_8.7 | | `qemu-kvm-tools` | Red Hat:enterprise_linux:6::computenode | All versions | 2:0.12.1.2-2.491.el6_8.7 | | `qemu-img-rhev` | Red Hat:enterprise_linux:6::hypervisor | All versions | 2:0.12.1.2-2.491.el6_8.7 | | `qemu-kvm-rhev` | Red Hat:enterprise_linux:6::hypervisor | All versions | 2:0.12.1.2-2.491.el6_8.7 | | `qemu-kvm-rhev-debuginfo` | Red Hat:enterprise_linux:6::hypervisor | All versions | 2:0.12.1.2-2.491.el6_8.7 | | `qemu-kvm-rhev-tools` | Red Hat:enterprise_linux:6::hypervisor | All versions | 2:0.12.1.2-2.491.el6_8.7 | | `qemu-guest-agent` | Red Hat:enterprise_linux:6::server | All versions | 2:0.12.1.2-2.491.el6_8.7 | | `qemu-img` | Red Hat:enterprise_linux:6::server | All versions | 2:0.12.1.2-2.491.el6_8.7 | | `qemu-kvm` | Red Hat:enterprise_linux:6::server | All versions | 2:0.12.1.2-2.491.el6_8.7 | | `qemu-kvm-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 2:0.12.1.2-2.491.el6_8.7 | | `qemu-kvm-tools` | Red Hat:enterprise_linux:6::server | All versions | 2:0.12.1.2-2.491.el6_8.7 | | `qemu-guest-agent` | Red Hat:enterprise_linux:6::workstation | All versions | 2:0.12.1.2-2.491.el6_8.7 | | `qemu-img` | Red Hat:enterprise_linux:6::workstation | All versions | 2:0.12.1.2-2.491.el6_8.7 | | `qemu-kvm` | Red Hat:enterprise_linux:6::workstation | All versions | 2:0.12.1.2-2.491.el6_8.7 | | `qemu-kvm-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 2:0.12.1.2-2.491.el6_8.7 | | `qemu-kvm-tools` | Red Hat:enterprise_linux:6::workstation | All versions | 2:0.12.1.2-2.491.el6_8.7 | Products: Citrix Xenserver, Debian Debian Linux, Qemu Qemu, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Eus, Redhat Enterprise Linux Workstation, Redhat Openstack, Xen Xen. ## How do I fix CVE-2017-2620? Upgrade to a fixed version. ## Is CVE-2017-2620 being exploited? There is no known exploitation of CVE-2017-2620 in the wild and no public exploit code. ## Other vulnerabilities in Citrix Xenserver - [CVE-2014-4947](https://insights.sbomify.com/CVE-2014-4947/): Memory corruption in n/a (critical 10.0) - [CVE-2018-14007](https://insights.sbomify.com/CVE-2018-14007/): Path traversal in n/a (critical 9.8) - [CVE-2015-7705](https://insights.sbomify.com/CVE-2015-7705/): Denial of service in n/a (critical 9.8) - [CVE-2016-5302](https://insights.sbomify.com/CVE-2016-5302/): Auth bypass in n/a (critical 9.8) - [CVE-2017-12134](https://insights.sbomify.com/CVE-2017-12134/): Memory corruption in n/a (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2017-2620 and fix it if it is affected. What it is: CVE-2017-2620 is a medium-severity memory corruption vulnerability in Citrix Xenserver, 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-2620 in the wild and no public exploit code. Affected product: Citrix Xenserver. 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-2620/ (Markdown: https://insights.sbomify.com/CVE-2017-2620/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-2620 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-2620 - OSV: https://osv.dev/vulnerability/CVE-2017-2620 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-2620/ Summaries are generated and may contain mistakes; the official description above is the record.