Enterprise LinuxOperating system · Redhat
CVE-2015-3247
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 · uneditedRace condition in the worker_update_monitors_config function in SPICE 0.12.4 allows a remote authenticated guest user to cause a denial of service (heap-based memory corruption and QEMU-KVM crash) or possibly execute arbitrary code on the host via unspecified vectors.
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 confidenceRace condition in the worker_update_monitors_config function in SPICE 0.12.4 allows a remote authenticated guest user to cause heap-based memory corruption leading to QEMU-KVM crash or potentially execute arbitrary code on the host via unspecified vectors.
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 LinuxOperating system
= 6.0= 7.0
Enterprise Linux DesktopOperating system
= 6.0= 7.0
Enterprise Linux Hpc NodeOperating system
= 6= 7.0
Enterprise Linux ServerOperating system
= 6.0= 7.0
Enterprise Linux WorkstationOperating system
= 6.0= 7.0= 0.12.4CVSS 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
- Local
- Complexity
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:M/Au:N/C:C/I:C/A:C
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed SPICE versionRun the command to query the SPICE server version (e.g., rpm query, dpkg query, or check the binary version depending on your system)Affected if The installed version is exactly 0.12.4 or falls within the affected Red Hat Enterprise Linux 6.0/7.0 SPICE packages
-
Confirm QEMU-KVM is using SPICEInspect running QEMU-KVM processes or configuration files to verify the SPICE display device or SPICE server is enabledAffected if QEMU-KVM is configured with SPICE display emulation and the SPICE server is active
-
Check for remote guest connection accessReview SPICE server configuration or QEMU command-line arguments for SPICE listening interfaces and portsAffected if SPICE is configured to accept remote or guest connections from network interfaces (not only local Unix socket)
-
Verify authenticated guest sessions are permittedExamine SPICE authentication settings and determine whether unauthenticated or authenticated guest access is allowedAffected if SPICE permits guest users to connect without strong authentication controls
You are affected if SPICE version 0.12.4 is installed AND QEMU-KVM is actively using the SPICE server with remote guest connection capability enabled.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade SPICE to a patched version or apply vendor-specific patch addressing the race condition in worker_update_monitors_config; ensure proper synchronization around monitor configuration updates.
Fix this in Enterprise Linux
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-3247 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-3247 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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