CVE-2017-12194

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-14. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 6%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

A flaw was found in the way spice-client processed certain messages sent from the server. An attacker, having control of malicious spice-server, could use this flaw to crash the client or execute arbitrary code with permissions of the user running the client. spice-gtk versions through 0.34 are believed to be vulnerable.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
91.9%
KEV
Not listed

Published

March 14, 2018

Last Modified

November 21, 2024

Advisory Details (3)

Auto-updated Jun 6, 2026
Patch available. Sources: redhat.
generic

spice-gtk: Remote code execution (GLSA 201811-20) — Gentoo security

https://security.gentoo.org/glsa/201811-20
redhat Patch Available

1501200 – (CVE-2017-12194) CVE-2017-12194 spice-gtk: Integer overflows causing buffer overflows in spice-client

https://bugzilla.redhat.com/show_bug.cgi?id=1501200
generic
http://www.securityfocus.com/bid/103413

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuspice-client (0.12.4-0nocelt2ubuntu1.6) @ trusty2026-05-28ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 6× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:24 UTCEPSS rescore
  2. 2026-07-09 19:06 UTCEPSS rescore
  3. 2026-07-08 15:10 UTCEPSS rescore
  4. 2026-07-06 16:24 UTCEPSS rescore
  5. 2026-07-06 02:20 UTCEPSS rescore
  6. 2026-07-05 02:27 UTCEPSS rescore
  7. 2026-07-04 11:56 UTCOSV refresh
  8. 2026-07-04 06:28 UTCEPSS rescore
  9. 2026-07-01 15:02 UTCEPSS rescore
  10. 2026-07-01 15:02 UTCEPSS rescore
  11. 2026-06-30 23:19 UTCEPSS rescore
  12. 2026-06-30 23:19 UTCEPSS rescore
  13. 2026-06-29 14:03 UTCEPSS rescore
  14. 2026-06-28 14:04 UTCEPSS rescore
  15. 2026-06-28 04:53 UTCEPSS rescore
  16. 2026-06-27 03:05 UTCEPSS rescore
  17. 2026-06-25 13:47 UTCEPSS rescore
  18. 2026-06-25 13:47 UTCEPSS rescore
  19. 2026-06-24 14:02 UTCEPSS rescore
  20. 2026-06-23 21:30 UTCEPSS rescore
  21. 2026-06-21 14:54 UTCEPSS rescore
  22. 2026-06-21 14:54 UTCEPSS rescore
  23. 2026-06-21 01:57 UTCEPSS rescore
  24. 2026-06-21 01:57 UTCEPSS rescore
  25. 2026-06-19 19:23 UTCEPSS rescore
Show 41 more
  1. 2026-06-19 19:23 UTCEPSS rescore
  2. 2026-06-18 17:50 UTCEPSS rescore
  3. 2026-06-17 17:50 UTCEPSS rescore
  4. 2026-06-16 17:50 UTCEPSS rescore
  5. 2026-06-15 23:39 UTCOSV refresh
  6. 2026-06-15 17:45 UTCEPSS rescore
  7. 2026-06-14 23:14 UTCEPSS rescore
  8. 2026-06-14 23:14 UTCEPSS rescore
  9. 2026-06-13 22:57 UTCEPSS rescore
  10. 2026-06-12 23:09 UTCEPSS rescore
  11. 2026-06-11 13:57 UTCEPSS rescore
  12. 2026-06-10 22:15 UTCEPSS rescore
  13. 2026-06-08 14:14 UTCEPSS rescore
  14. 2026-06-07 15:22 UTCEPSS rescore
  15. 2026-06-07 15:22 UTCEPSS rescore
  16. 2026-06-06 13:45 UTCEPSS rescore
  17. 2026-06-06 13:45 UTCEPSS rescore
  18. 2026-06-05 22:44 UTCEPSS rescore
  19. 2026-06-05 06:08 UTCEPSS rescore
  20. 2026-06-05 06:08 UTCEPSS rescore
  21. 2026-06-04 13:10 UTCEPSS rescore
  22. 2026-06-04 13:10 UTCEPSS rescore
  23. 2026-06-02 20:11 UTCEPSS rescore
  24. 2026-06-02 20:11 UTCEPSS rescore
  25. 2026-06-01 13:49 UTCEPSS rescore
  26. 2026-06-01 13:49 UTCEPSS rescore
  27. 2026-05-31 22:28 UTCEPSS rescore
  28. 2026-05-31 00:14 UTCEPSS rescore
  29. 2026-05-29 13:41 UTCEPSS rescore
  30. 2026-05-28 13:42 UTCEPSS rescore
  31. 2026-05-28 13:42 UTCEPSS rescore
  32. 2026-05-28 10:26 UTCEG score recompute
  33. 2026-05-28 10:26 UTCVendor advisory
  34. 2026-05-28 10:26 UTCGHSA enrichment
  35. 2026-05-27 13:38 UTCEPSS rescore
  36. 2026-05-27 13:38 UTCEPSS rescore
  37. 2026-05-26 13:42 UTCEPSS rescore
  38. 2026-05-26 13:42 UTCEPSS rescore
  39. 2026-05-26 07:17 UTCEPSS rescore
  40. 2026-05-26 07:17 UTCEPSS rescore
  41. 2026-05-23 18:05 UTCOSV refresh

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2017-12194?
CVE-2017-12194 is a critical vulnerability published on March 14, 2018. A flaw was found in the way spice-client processed certain messages sent from the server. An attacker, having control of malicious spice-server, could use this flaw to crash the client or execute arbitrary code with permissions of the user running the client. spice-gtk versions through 0.34 are…
When was CVE-2017-12194 disclosed?
CVE-2017-12194 was first published in the National Vulnerability Database on March 14, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-12194 actively exploited?
CVE-2017-12194 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 91.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-12194?
CVE-2017-12194 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-12194?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-12194, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-12194

Explore →

Is Your Infrastructure Affected by CVE-2017-12194?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs