# CVE-2017-7506: Memory corruption in spice > An authenticated attacker can cause a crash or memory leak in the SPICE server via crafted messages, leading to denial of service or information disclosure. - **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 18 Jul 2017 - **Updated:** 5 Aug 2024 - **Also known as:** ALPINE-CVE-2017-7506, DEBIAN-CVE-2017-7506, DSA-3907-1, GHSA-3pjw-h9v6-f5x8, MGASA-2017-0239, RHBA-2017:2529, RHSA-2017:2471, RHSA-2018:3522, SUSE-SU-2017:1832-1, SUSE-SU-2017:1836-1, SUSE-SU-2017:1837-1, SUSE-SU-2017:1839-1, SUSE-SU-2017:2552-1, UBUNTU-CVE-2017-7506, USN-3355-1 ## What is CVE-2017-7506? CVE-2017-7506 is a high-severity memory corruption vulnerability in The SPICE Project spice, published on 18 Jul 2017. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description spice versions though 0.13 are vulnerable to out-of-bounds memory access when processing specially crafted messages from authenticated attacker to the spice server resulting into crash and/or server memory leak. Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) ## Which versions are affected by CVE-2017-7506? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `spice-server` | Red Hat:enterprise_linux:6::client | All versions | 0:0.12.4-16.el6_10.2 | | `spice-server-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:0.12.4-16.el6_10.2 | | `spice-server-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:0.12.4-16.el6_10.2 | | `spice-server` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.12.4-16.el6_10.2 | | `spice-server-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.12.4-16.el6_10.2 | | `spice-server-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.12.4-16.el6_10.2 | | `spice-server` | Red Hat:enterprise_linux:6::server | All versions | 0:0.12.4-16.el6_10.2 | | `spice-server-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:0.12.4-16.el6_10.2 | | `spice-server-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:0.12.4-16.el6_10.2 | | `spice-server` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.12.4-16.el6_10.2 | | `spice-server-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.12.4-16.el6_10.2 | | `spice-server-devel` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.12.4-16.el6_10.2 | | `spice` | Red Hat:enterprise_linux:7::client | All versions | 0:0.12.8-2.el7.1 | | `spice-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:0.12.8-2.el7.1 | | `spice-server` | Red Hat:enterprise_linux:7::client | All versions | 0:0.12.8-2.el7.1 | | `spice-server-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:0.12.8-2.el7.1 | | `spice` | Red Hat:enterprise_linux:7::computenode | All versions | 0:0.12.8-2.el7.1 | | `spice-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:0.12.8-2.el7.1 | | `spice-server` | Red Hat:enterprise_linux:7::computenode | All versions | 0:0.12.8-2.el7.1 | | `spice-server-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:0.12.8-2.el7.1 | | `imgbased` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:0.9.47-0.1.el7ev | | `ovirt-node-ng` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:4.1.5-0.20170810.0.el7 | | `ovirt-node-ng-nodectl` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:4.1.5-0.20170810.0.el7 | | `redhat-release-virtualization-host` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:4.1-5.0.el7 | | `redhat-virtualization-host` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:4.1-20170816.2.el7_4 | | `redhat-virtualization-host-image-update` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:4.1-20170816.2.el7_4 | | `redhat-virtualization-host-image-update-placeholder` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:4.1-5.0.el7 | | `spice` | Red Hat:enterprise_linux:7::server | All versions | 0:0.12.8-2.el7.1 | | `spice-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:0.12.8-2.el7.1 | | `spice-server` | Red Hat:enterprise_linux:7::server | All versions | 0:0.12.8-2.el7.1 | | `spice-server-devel` | Red Hat:enterprise_linux:7::server | All versions | 0:0.12.8-2.el7.1 | | `spice` | Red Hat:enterprise_linux:7::workstation | All versions | 0:0.12.8-2.el7.1 | | `spice-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 0:0.12.8-2.el7.1 | | `spice-server` | Red Hat:enterprise_linux:7::workstation | All versions | 0:0.12.8-2.el7.1 | | `spice-server-devel` | Red Hat:enterprise_linux:7::workstation | All versions | 0:0.12.8-2.el7.1 | | `spice` | SUSE:Linux Enterprise Desktop 12 SP2 | All versions | 0.12.7-10.3.1 | | `spice` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 0.12.8-3.9 | | `spice` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 0.12.4-11.1 | | `spice` | SUSE:Linux Enterprise Server 12 SP1-LTSS | All versions | 0.12.5-10.1 | | `spice` | SUSE:Linux Enterprise Server 12 SP2 | All versions | 0.12.7-10.3.1 | Products: Spice Project Spice. ## How do I fix CVE-2017-7506? Apply the vendor's patch. ## Is CVE-2017-7506 being exploited? There is no known exploitation of CVE-2017-7506 in the wild and no public exploit code. ## Other vulnerabilities in The SPICE Project spice - [CVE-2018-10893](https://insights.sbomify.com/CVE-2018-10893/): Integer overflow in spice-client (high 7.6) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2017-7506 and fix it if it is affected. What it is: CVE-2017-7506 is a high-severity memory corruption vulnerability in The SPICE Project spice, published on 18 Jul 2017. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2017-7506 in the wild and no public exploit code. Affected product: The SPICE Project spice. 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-7506/ (Markdown: https://insights.sbomify.com/CVE-2017-7506/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-7506 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-7506 - OSV: https://osv.dev/vulnerability/CVE-2017-7506 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-7506/ Summaries are generated and may contain mistakes; the official description above is the record.