# CVE-2015-5225: Memory corruption in n/a > A buffer overflow in QEMU's VNC driver allows guest users to crash the host or execute arbitrary code on the host system. - **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`) - **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:** 6 Nov 2015 - **Updated:** 6 Aug 2024 - **Also known as:** DEBIAN-CVE-2015-5225, GHSA-xf7r-x3p2-rg72, RHSA-2015:1772, RHSA-2015:1837 ## What is CVE-2015-5225? CVE-2015-5225 is a high-severity memory corruption vulnerability in Fedoraproject Fedora, published on 6 Nov 2015. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Buffer overflow in the vnc_refresh_server_surface function in the VNC display driver in QEMU before 2.4.0.1 allows guest users to cause a denial of service (heap memory corruption and process crash) or possibly execute arbitrary code on the host via unspecified vectors, related to refreshing the server display surface. Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) ## Which versions are affected by CVE-2015-5225? It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libcacard-devel-rhev` | Red Hat:enterprise_linux:7::hypervisor | All versions | 10:2.1.2-23.el7_1.9 | | `libcacard-rhev` | Red Hat:enterprise_linux:7::hypervisor | All versions | 10:2.1.2-23.el7_1.9 | | `libcacard-tools-rhev` | Red Hat:enterprise_linux:7::hypervisor | All versions | 10:2.1.2-23.el7_1.9 | | `qemu-img-rhev` | Red Hat:enterprise_linux:7::hypervisor | All versions | 10:2.1.2-23.el7_1.9 | | `qemu-kvm-common-rhev` | Red Hat:enterprise_linux:7::hypervisor | All versions | 10:2.1.2-23.el7_1.9 | | `qemu-kvm-rhev` | Red Hat:enterprise_linux:7::hypervisor | All versions | 10:2.1.2-23.el7_1.9 | | `qemu-kvm-rhev-debuginfo` | Red Hat:enterprise_linux:7::hypervisor | All versions | 10:2.1.2-23.el7_1.9 | | `qemu-kvm-tools-rhev` | Red Hat:enterprise_linux:7::hypervisor | All versions | 10:2.1.2-23.el7_1.9 | | `libcacard-devel-rhev` | Red Hat:openstack:5::el7 | All versions | 10:2.1.2-23.el7_1.9 | | `libcacard-rhev` | Red Hat:openstack:5::el7 | All versions | 10:2.1.2-23.el7_1.9 | | `libcacard-tools-rhev` | Red Hat:openstack:5::el7 | All versions | 10:2.1.2-23.el7_1.9 | | `qemu-img-rhev` | Red Hat:openstack:5::el7 | All versions | 10:2.1.2-23.el7_1.9 | | `qemu-kvm-common-rhev` | Red Hat:openstack:5::el7 | All versions | 10:2.1.2-23.el7_1.9 | | `qemu-kvm-rhev` | Red Hat:openstack:5::el7 | All versions | 10:2.1.2-23.el7_1.9 | | `qemu-kvm-rhev-debuginfo` | Red Hat:openstack:5::el7 | All versions | 10:2.1.2-23.el7_1.9 | | `qemu-kvm-tools-rhev` | Red Hat:openstack:5::el7 | All versions | 10:2.1.2-23.el7_1.9 | | `libcacard-devel-rhev` | Red Hat:openstack:6::el7 | All versions | 10:2.1.2-23.el7_1.9 | | `libcacard-rhev` | Red Hat:openstack:6::el7 | All versions | 10:2.1.2-23.el7_1.9 | | `libcacard-tools-rhev` | Red Hat:openstack:6::el7 | All versions | 10:2.1.2-23.el7_1.9 | | `qemu-img-rhev` | Red Hat:openstack:6::el7 | All versions | 10:2.1.2-23.el7_1.9 | | `qemu-kvm-common-rhev` | Red Hat:openstack:6::el7 | All versions | 10:2.1.2-23.el7_1.9 | | `qemu-kvm-rhev` | Red Hat:openstack:6::el7 | All versions | 10:2.1.2-23.el7_1.9 | | `qemu-kvm-rhev-debuginfo` | Red Hat:openstack:6::el7 | All versions | 10:2.1.2-23.el7_1.9 | | `qemu-kvm-tools-rhev` | Red Hat:openstack:6::el7 | All versions | 10:2.1.2-23.el7_1.9 | | `libcacard-rhev` | Red Hat:openstack:7::el7 | All versions | 10:2.1.2-23.el7_1.9 | | `libcacard-tools-rhev` | Red Hat:openstack:7::el7 | All versions | 10:2.1.2-23.el7_1.9 | | `qemu-img-rhev` | Red Hat:openstack:7::el7 | All versions | 10:2.1.2-23.el7_1.9 | | `qemu-kvm-common-rhev` | Red Hat:openstack:7::el7 | All versions | 10:2.1.2-23.el7_1.9 | | `qemu-kvm-rhev` | Red Hat:openstack:7::el7 | All versions | 10:2.1.2-23.el7_1.9 | | `qemu-kvm-rhev-debuginfo` | Red Hat:openstack:7::el7 | All versions | 10:2.1.2-23.el7_1.9 | | `qemu-kvm-tools-rhev` | Red Hat:openstack:7::el7 | All versions | 10:2.1.2-23.el7_1.9 | Products: Fedoraproject Fedora, Qemu Qemu, Redhat Openstack. ## How do I fix CVE-2015-5225? Upgrade to a fixed version. ## Is CVE-2015-5225 being exploited? There is no known exploitation of CVE-2015-5225 in the wild and no public exploit code. ## Other vulnerabilities in Fedoraproject Fedora - [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild) - [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild) - [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2015-5225 and fix it if it is affected. What it is: CVE-2015-5225 is a high-severity memory corruption vulnerability in Fedoraproject Fedora, published on 6 Nov 2015. 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-2015-5225 in the wild and no public exploit code. Affected product: Fedoraproject Fedora. 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-2015-5225/ (Markdown: https://insights.sbomify.com/CVE-2015-5225/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2015-5225 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-5225 - OSV: https://osv.dev/vulnerability/CVE-2015-5225 --- From sbomify Insights: https://insights.sbomify.com/CVE-2015-5225/ Summaries are generated and may contain mistakes; the official description above is the record.