CVE-2016-9603 — CVE & Security Advisory Radar

🎯 CVE-2016-9603 MEDIUM 5.5 🔥 EPSS 4.5% 🇪🇺 EUVD

📄 .md Alle CVEs anzeigen ✕

CVE-2016-9603 | A heap buffer overflow flaw was found in QEMU's Cirrus CLGD 54xx VGA emulator's VNC display driver support before 2.9; the issue could occur when a VNC client attempted to update its display after a VGA operation is performed by a guest. A privileged user/process inside a guest could use this flaw to crash the QEMU process or, potentially, execute arbitrary code on the host with privileges of the QEMU process.

A heap buffer overflow flaw was found in QEMU's Cirrus CLGD 54xx VGA emulator's VNC display driver support before 2.9; the issue could occur when a VNC client attempted to update its display after a VGA operation is performed by a guest. A privileged user/process inside a guest could use this flaw to crash the QEMU process or, potentially, execute arbitrary code on the host with privileges of the QEMU process.

Klassifikation & Betroffenheit:

qemu Qemu: 2.9qemu qemu *citrix xenserver 6.0.2citrix xenserver 6.2.0citrix xenserver 6.5citrix xenserver 7.0citrix xenserver 7.1redhat openstack 5.0

Improper Restriction of Operations within the Bounds of a Memory Buffer 🎯 High

The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.

🛡️ Empfohlene Mitigation: Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow prot…

Vollständige Definition bei MITRE ➔

⚔️ Typische Angriffsmuster (CAPEC):

CAPEC-10 · Buffer Overflow via Environment Variable… (High) CAPEC-14 · Client-side Injection-induced Buffer Ove… (High) CAPEC-24 · Filter Failure through Buffer Overflow (High) CAPEC-42 · MIME Conversion (High) CAPEC-44 · Overflow Binary Resource File (Very High) CAPEC-45 · Buffer Overflow via Symbolic Links (High) CAPEC-100 · Overflow Buffers (Very High) CAPEC-123 · Buffer Manipulation (Very High)

🧩 Ähnliche Schwachstellen (Hersteller/Klasse/Score-Band):

CVE-2017-15119 5.8 CVE-2017-2620 5.5 CVE-2017-2630 5.5 CVE-2017-2615 5.5 CVE-2017-2633 5.4

🩹 Patch verfügbar (OSV):

🩹 359c41abe32638adad503e386969fa428cecff52 (Commit) 🩹 359c41abe32638adad503e386969fa428cecff52 (Commit)

📚 Referenzen & Quellen:

🇪🇺 Original-Eintrag (ENISA EUVD) 🇺🇸 NVD-Eintrag

Ausnutzungs-Zeitleiste:

Reserviert 2016

Veröffentlicht 07/2018

Heute 10.09.

CVSS-Vektor-Analyse: 5.5

AV · Angriffsvektor Benachbart

AC · Komplexität Hoch

PR · Privilegien Gering

UI · Interaktion Keine

S · Scope Verändert

C · Vertraulichkeit Gering

I · Integrität Gering

A · Verfügbarkeit Gering

CVSS:3.0/AV:A/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L

Veröffentlicht:27.07.2018

Aktualisiert:17.06.2026 00:56

Assigner (CNA):redhat

EUVD-ID:EUVD-2016-10407

Quellen: 🇪🇺 EUVD-Datenbank (ENISA) + 🇺🇸 NVD-Anreicherung · 24-h-Cache

CWE-119: Memory Corruption ✓ Offizieller Patch / Advisory verfügbar

💡 Gegenmaßnahme: Sicherheits-Update des Herstellers zeitnah einspielen und Netzwerksegmentierung prüfen.

Tier	2026-08-29	2026-09-06
≥90 %	4	0
≥50 %	4	0
≥10 %	3	0
<10 %	304	300

5.5 MEDIUM

🇪🇺 EUVD

EPSS

4.5%

CVE-2016-9603 🌐 Adjacent Network 🔑 Geringe Nutzerrechte nötig

qemu

CVE-2016-9603 | A heap buffer overflow flaw was found in QEMU's Cirrus CLGD 54xx VGA emulator's VNC display driver support before 2.9; the issue could occur when a VNC client attempted to update its display after a VGA operation is performed by a guest. A privileged user/process inside a guest could use this flaw to crash the QEMU process or, potentially, execute arbitrary code on the host with privileges of the QEMU process.

CWE-119: Memory Corruption ✓ Offizieller Patch / Advisory verfügbar

💡 Gegenmaßnahme: Sicherheits-Update des Herstellers zeitnah einspielen und Netzwerksegmentierung prüfen.

27.07.2018

🛡️ Details ➔

Zero-Day & Vulnerability Intelligence Hub