Vulnerabilities
Misconfiguration
Compliance
CVE Vulnerabilities

CVE-2018-10893

Heap-based Buffer Overflow

Published: Sep 11, 2018 | Modified: Nov 21, 2024
CVSS 3.x
8.8
HIGH
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
6.5 MEDIUM
AV:N/AC:L/Au:S/C:P/I:P/A:P
RedHat/V2
RedHat/V3
7.6 MODERATE
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L
Ubuntu
MEDIUM
Vulnerability-free packages from our partners
root.io logo minimus.io logo echo.ai logo
Additional information
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2018-10893
CWEhttps://cwe.mitre.org/data/definitions/122.html

Multiple integer overflow and buffer overflow issues were discovered in spice-clients handling of LZ compressed frames. A malicious server could cause the client to crash or, potentially, execute arbitrary code.

Weakness

A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().

Affected Software

NameVendorStart VersionEnd Version
SpiceSpice_project- (including)- (including)
Red Hat Enterprise Linux 6RedHatspice-gtk-0:0.26-8.el6_10.2*
Red Hat Enterprise Linux 7RedHatlibgovirt-0:0.3.4-3.el7*
Red Hat Enterprise Linux 7RedHatspice-gtk-0:0.35-4.el7*
Red Hat Enterprise Linux 7RedHatspice-vdagent-0:0.14.0-18.el7*
Red Hat Enterprise Linux 7RedHatvirt-viewer-0:5.0-15.el7*
Spice-gtkUbuntuartful*
Spice-gtkUbuntubionic*
Spice-gtkUbuntucosmic*
Spice-gtkUbuntudevel*
Spice-gtkUbuntudisco*
Spice-gtkUbuntueoan*
Spice-gtkUbuntuesm-apps/bionic*
Spice-gtkUbuntuesm-apps/focal*
Spice-gtkUbuntuesm-apps/jammy*
Spice-gtkUbuntuesm-apps/noble*
Spice-gtkUbuntuesm-apps/xenial*
Spice-gtkUbuntufocal*
Spice-gtkUbuntugroovy*
Spice-gtkUbuntuhirsute*
Spice-gtkUbuntuimpish*
Spice-gtkUbuntujammy*
Spice-gtkUbuntukinetic*
Spice-gtkUbuntulunar*
Spice-gtkUbuntumantic*
Spice-gtkUbuntunoble*
Spice-gtkUbuntuoracular*
Spice-gtkUbuntuplucky*
Spice-gtkUbuntuquesting*
Spice-gtkUbuntutrusty*
Spice-gtkUbuntuxenial*

Potential Mitigations

  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking.
  • D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
  • Run or compile the software using features or extensions that randomly arrange the positions of a program’s executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code.
  • Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as “rebasing” (for Windows) and “prelinking” (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking.
  • For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335].

References

Aqua Security is the largest pure-play cloud native security company, providing customers the freedom to innovate and run their businesses with minimal friction. The Aqua Cloud Native Security Platform provides prevention, detection, and response automation across the entire application lifecycle to secure the build, secure cloud infrastructure and secure running workloads wherever they are deployed.
Copyright © 2026 Aqua Security Software Ltd.   Privacy Policy | Terms of Use