Spice ActivexApplication · Redhat
CVE-2010-2793
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 SPICE (aka spice-activex) plug-in for Internet Explorer in Red Hat Enterprise Virtualization (RHEV) Manager before 2.2.4 allows local users to create a certain named pipe, and consequently gain privileges, via vectors involving knowledge of the name of this named pipe, in conjunction with use of the ImpersonateNamedPipeClient function.
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 SPICE ActiveX plugin for Internet Explorer allows local users to pre-create a named pipe with known name and then impersonate clients connecting to it via ImpersonateNamedPipeClient, resulting in privilege escalation. The vulnerability exists in RHHEV Manager versions prior to 2.2.4.
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
Spice ActivexApplication
all versions
Enterprise Virtualization ManagerOperating system
<= 2.2.3= 2.1= 2.2CVSS 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
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 if SPICE ActiveX plugin is installedCheck for the SPICE ActiveX control on the system. Look in the Windows registry under HKLM\SOFTWARE\Microsoft\Code Store Database\Distributed COM or HKCR\CLSID for entries containing 'SPICE' or ' spice ' related ActiveX controls. Alternatively, check for spic全.dll or similar SPICE-related DLLs in Program Files directories.Affected if SPICE ActiveX plugin for Internet Explorer is present on the system.
-
Check Red Hat Enterprise Virtualization Manager versionLocate the RHHEV Manager installation and check its version. Common locations include C:\Program Files\RedHat\ or the installation directory. Use 'reg query' on Windows or check the RPM/database version if on Linux: rpm -q rhev-manager or check the manager's about/info page in the admin console.Affected if The installed version is 2.1, 2.2, or any version <= 2.2.3.
-
Verify the named pipe service is configuredThe vulnerability involves a named pipe that SPICE uses. Check if the SPICE session service is running and configured. On Windows, use 'sc query' or check services.msc for SPICE-related services. On Linux, check for spicec or related processes.Affected if SPICE services are running and the named pipe interface is enabled for client connections.
-
Check for presence of the vulnerable named pipeThe flaw involves a race condition where a local user can pre-create a named pipe with a known name before the SPICE service creates it. Monitor or check for writable pipe directories (commonly \\pipe\ or similar) that the SPICE service uses.Affected if The SPICE ActiveX creates a named pipe in a location where unprivileged local users can create pipes with predictable names.
The system is affected if the SPICE ActiveX plugin is installed and the RHHEV Manager version is 2.1, 2.2, or any version up to and including 2.2.3, with SPICE services 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 Red Hat Enterprise Virtualization Manager to version 2.2.4 or later to obtain the patch for this vulnerability.
Fix this in Spice Activex
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-2793 — 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-2010-2793 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