Spice vulnerabilitiesRanked by how likely they are to be used.
Spice is made by Spice Project. We track 15 published vulnerabilities in it, across 37 versions. None of them is on the list of flaws known to be exploited today. If you run Spice, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Spice vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Spice's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Spice flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 8.5%CVE-2016-0749Critical
The smartcard interaction in SPICE allows remote attackers to cause a denial of service (QEMU-KVM process crash) or possibly execute arbitrary code via vectors related to connecting to a guest VM, which triggers a...
- 4.2%CVE-2017-7506High
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.
- 3.9%CVE-2018-10873High
A vulnerability was discovered in SPICE before version 0.14.1 where the generated code used for demarshalling messages lacked sufficient bounds checks.
- 3.8%CVE-2016-9577High
A vulnerability was discovered in SPICE before 0.13.90 in the server's protocol handling.
- 2.7%CVE-2013-4282Medium
Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket.
- 2.7%CVE-2021-20201Medium
A flaw was found in spice in versions before 0.14.92.
- 2.7%CVE-2020-14355Medium
Multiple buffer overflow vulnerabilities were found in the QUIC image decoding process of the SPICE remote display system, before spice-0.14.2-1.
- 2.6%CVE-2013-4130Medium
The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a...
- 2.5%CVE-2016-9578High
A vulnerability was discovered in SPICE before 0.13.90 in the server's protocol handling.
- 2.4%CVE-2018-10893High
Multiple integer overflow and buffer overflow issues were discovered in spice-client's handling of LZ compressed frames.
Running Spice? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
The smartcard interaction in SPICE allows remote attackers to cause a denial of service (QEMU-KVM process crash) or possibly execute arbitrary code via vectors related to connecting to a guest VM, which triggers a heap-based buffer overflow.
- Matched to
- Spice on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 15 published vulnerabilities listed under the name Spice, across 37 versions.
None of Spice's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Spice. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.