Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2019-3813: Spice, versions 0.5.2 through 0.14.1, are vulnerable to an out-of-bounds read due to an off-by-one error in me

48
This month
HIGH 7.5WATCHLISTUPGRADEMITIGATEMITIGATE

CVE-2019-3813 is a high-severity flaw (CVSS 7.5) affecting spice, enterprise linux desktop, enterprise linux server. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Spice, versions 0.5.2 through 0.14.1, are vulnerable to an out-of-bounds read due to an off-by-one error in memslot_get_virt. This may lead to a denial of service, or, in the worst case, code-execution by unauthenticated attackers.

Why this priority

  • High severity
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score7.5 (High)
Attack vectorAdjacent network
Attack complexityHigh
Privileges neededNone
User interactionNone
EPSS exploit chance1.2% (top 32%)
CISA exploited listNo
WeaknessCWE-193
Published2019-02-04
Last modified2026-06-17
Publisher (CNA): Red Hat, Inc. · Vendor: redhat · spice project

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

spice project spice UPGRADE
Affected: >= 0.5.2 and <= 0.14.1
Fixed in: newer than 0.14.1
Safe to downgrade to: a release before 0.5.2
1. Check installed version
apt-cache policy spice || rpm -q spice || spice --version
2. UPGRADE to newer than 0.14.1 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade spice
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade spice
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 0.5.2 (Debian / Ubuntu)
apt-cache madison spice sudo apt install spice=<VERSION_BEFORE_0.5.2> sudo apt-mark hold spice
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list spice sudo dnf downgrade spice-<VERSION_BEFORE_0.5.2> sudo dnf versionlock add spice
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
redhat enterprise linux desktop MITIGATE
Affected: 6.0 · 7.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 6.0
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
redhat enterprise linux server MITIGATE
Affected: 6.0 · 7.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 6.0
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
redhat enterprise linux server aus MITIGATE
Affected: 7.6
Fixed in: no fixed release known
Safe to downgrade to: a release before 7.6
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
redhat enterprise linux server eus MITIGATE
Affected: 7.6
Fixed in: no fixed release known
Safe to downgrade to: a release before 7.6
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
redhat enterprise linux server tus MITIGATE
Affected: 7.6
Fixed in: no fixed release known
Safe to downgrade to: a release before 7.6
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-3813?

spice: upgrade to newer than 0.14.1; enterprise linux desktop: mitigate or apply the listed mitigation; enterprise linux server: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2019-3813 being exploited?

CVE-2019-3813 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-3813 affect?

CVE-2019-3813 affects spice, enterprise linux desktop, enterprise linux server. Severity is high (CVSS 7.5). Spice, versions 0.5.2 through 0.14.1, are vulnerable to an out-of-bounds read due to an off-by-one error in memslot_get_virt. This may lead to a denial of service, or, in the worst case, code-execution by unauthenticated attackers.

How urgent is CVE-2019-3813?

Priority 48/100. High severity; On your watchlist

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.