dbcve.org
Enterprise Linux DesktopOperating system · Redhat

CVE-2019-3813

HIGH · 7.5 CVSS v3.1 Published 2019-02-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Spice versions 0.5.2 through 0.14.1 contain an out-of-bounds read vulnerability in the memslot_get_virt function caused by an off-by-one error. This memory safety flaw can be exploited by unauthenticated remote attackers to potentially achieve code execution, though denial of service is the more likely outcome.

MitigationUpgrade Spice to version 0.14.2 or later, which contains the patch addressing the off-by-one error in memslot_get_virt. If upgrade is not immediately feasible, network-level access controls limiting exposure of the Spice service may reduce exploitability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Enterprise Linux DesktopOperating system
Affected:= 6.0= 7.0
Enterprise Linux ServerOperating system
Affected:= 6.0= 7.0
Enterprise Linux Server AusOperating system
Affected:= 7.6
Enterprise Linux Server EusOperating system
Affected:= 7.6
Enterprise Linux Server TusOperating system
Affected:= 7.6
Enterprise Linux WorkstationOperating system
Affected:= 6.0= 7.0
Debian LinuxOperating system
Affected:= 8.0= 9.0
Ubuntu LinuxOperating system
Affected:= 14.04= 16.04= 18.04= 18.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Spice software is installed
    Look for packages or services related to Spice on the system, such as spice-server, spice-protocol, or the Spice daemon process
    Affected if Spice is not installed on the system (not vulnerable)
  2. Determine the installed Spice version
    Query the installed Spice package version using the system's package manager (for example: rpm -q, dpkg -l, or apt list) or check the version of the spice-server library
    Affected if The installed version falls within 0.5.2 through 0.14.1 (inclusive)
  3. Verify the memslot_get_virt function is in use
    Confirm that the Spice service is actively running or that applications link against the affected libspice-server library
    Affected if Spice is actively running or linked by virtualization workloads (the vulnerability is only triggerable when this code path is exercised)
  4. Check system architecture for virtual machine usage
    Examine if the host runs QEMU/KVM virtual machines configured to use SPICE for display or peripheral redirection
    Affected if QEMU/KVM with SPICE display devices is configured, as this is the primary context where memslot_get_virt is invoked

The environment is affected if Spice is installed and the version is between 0.5.2 and 0.14.1 inclusive, with the Spice service actively handling virtual machine display or redirection workloads.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Spice to version 0.14.2 or later, which contains the patch addressing the off-by-one error in memslot_get_virt. If upgrade is not immediately feasible, network-level access controls limiting exposure of the Spice service may reduce exploitability.

Fix this in Enterprise Linux Desktop Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-3813 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-3813 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data