# CVE-2018-10893: Integer overflow in spice-client > A malicious server can trigger integer and buffer overflows in the SPICE client, leading to crashes or arbitrary code execution. - **Severity:** High 7.6 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 11 Sep 2018 - **Updated:** 5 Aug 2024 - **Also known as:** DEBIAN-CVE-2018-10893, GHSA-5jqv-xfc2-wmwv, RHSA-2019:2229, RHSA-2020:0471, UBUNTU-CVE-2018-10893 ## What is CVE-2018-10893? CVE-2018-10893 is a high-severity vulnerability in Red Hat spice-client, published on 11 Sep 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description Multiple integer overflow and buffer overflow issues were discovered in spice-client's handling of LZ compressed frames. A malicious server could cause the client to crash or, potentially, execute arbitrary code. Weakness: CWE-190 (Integer Overflow or Wraparound), CWE-122 (Heap-based Buffer Overflow) ## Which versions are affected by CVE-2018-10893? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `spice-glib` | Red Hat:enterprise_linux:6::client | All versions | 0:0.26-8.el6_10.2 | | `spice-glib-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:0.26-8.el6_10.2 | | `spice-gtk` | Red Hat:enterprise_linux:6::client | All versions | 0:0.26-8.el6_10.2 | | `spice-gtk-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:0.26-8.el6_10.2 | | `spice-gtk-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:0.26-8.el6_10.2 | | `spice-gtk-python` | Red Hat:enterprise_linux:6::client | All versions | 0:0.26-8.el6_10.2 | | `spice-gtk-tools` | Red Hat:enterprise_linux:6::client | All versions | 0:0.26-8.el6_10.2 | | `spice-glib` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.26-8.el6_10.2 | | `spice-glib-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.26-8.el6_10.2 | | `spice-gtk` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.26-8.el6_10.2 | | `spice-gtk-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.26-8.el6_10.2 | | `spice-gtk-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.26-8.el6_10.2 | | `spice-gtk-python` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.26-8.el6_10.2 | | `spice-gtk-tools` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.26-8.el6_10.2 | | `spice-glib` | Red Hat:enterprise_linux:6::server | All versions | 0:0.26-8.el6_10.2 | | `spice-glib-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:0.26-8.el6_10.2 | | `spice-gtk` | Red Hat:enterprise_linux:6::server | All versions | 0:0.26-8.el6_10.2 | | `spice-gtk-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:0.26-8.el6_10.2 | | `spice-gtk-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:0.26-8.el6_10.2 | | `spice-gtk-python` | Red Hat:enterprise_linux:6::server | All versions | 0:0.26-8.el6_10.2 | | `spice-gtk-tools` | Red Hat:enterprise_linux:6::server | All versions | 0:0.26-8.el6_10.2 | | `spice-glib` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.26-8.el6_10.2 | | `spice-glib-devel` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.26-8.el6_10.2 | | `spice-gtk` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.26-8.el6_10.2 | | `spice-gtk-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.26-8.el6_10.2 | | `spice-gtk-devel` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.26-8.el6_10.2 | | `spice-gtk-python` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.26-8.el6_10.2 | | `spice-gtk-tools` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.26-8.el6_10.2 | | `libgovirt` | Red Hat:enterprise_linux:7::client | All versions | 0:0.3.4-3.el7 | | `libgovirt-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:0.3.4-3.el7 | | `libgovirt-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:0.3.4-3.el7 | | `spice-glib` | Red Hat:enterprise_linux:7::client | All versions | 0:0.35-4.el7 | | `spice-glib-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:0.35-4.el7 | | `spice-gtk` | Red Hat:enterprise_linux:7::client | All versions | 0:0.35-4.el7 | | `spice-gtk-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:0.35-4.el7 | | `spice-gtk-tools` | Red Hat:enterprise_linux:7::client | All versions | 0:0.35-4.el7 | | `spice-gtk3` | Red Hat:enterprise_linux:7::client | All versions | 0:0.35-4.el7 | | `spice-gtk3-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:0.35-4.el7 | | `spice-gtk3-vala` | Red Hat:enterprise_linux:7::client | All versions | 0:0.35-4.el7 | | `spice-vdagent` | Red Hat:enterprise_linux:7::client | All versions | 0:0.14.0-18.el7 | Products: Spice Project Spice. ## How do I fix CVE-2018-10893? Apply the vendor's patch. ## Is CVE-2018-10893 being exploited? There is no known exploitation of CVE-2018-10893 in the wild and no public exploit code. ## Other vulnerabilities in Red Hat spice-client - [CVE-2017-7506](https://insights.sbomify.com/CVE-2017-7506/): Memory corruption in spice (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2018-10893 and fix it if it is affected. What it is: CVE-2018-10893 is a high-severity vulnerability in Red Hat spice-client, published on 11 Sep 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2018-10893 in the wild and no public exploit code. Affected product: Red Hat spice-client. 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-2018-10893/ (Markdown: https://insights.sbomify.com/CVE-2018-10893/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2018-10893 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-10893 - OSV: https://osv.dev/vulnerability/CVE-2018-10893 --- From sbomify Insights: https://insights.sbomify.com/CVE-2018-10893/ Summaries are generated and may contain mistakes; the official description above is the record.