Enterprise VirtualizationApplication · Redhat
CVE-2013-2152
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 · uneditedUnquoted Windows search path vulnerability in the SPICE service, as used in Red Hat Enterprise Virtualization (RHEV) 3.2, allows local users to gain privileges via a crafted application in an unspecified folder.
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 · moderate confidenceUnquoted Windows service path vulnerability in the SPICE service (used in Red Hat Enterprise Virtualization 3.2) allows local privilege escalation. The service executable path contains spaces and is not enclosed in quotes, causing Windows to search for executables in intermediate directories. Attackers can place malicious executables in these paths to gain elevated privileges when the service starts.
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 VirtualizationApplication
= 3.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
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/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.
-
Confirm SPICE service presenceOpen Windows Services console (services.msc) or run 'sc queryex type= service state= all' and search for a SPICE-related serviceAffected if No SPICE service is found on the system - the vulnerability does not apply
-
Retrieve the SPICE service executable pathRun 'sc qc <spice_service_name>' in Command Prompt to query the service configuration, noting the BINARY_PATH_NAME fieldAffected if The service exists but the BINARY_PATH_NAME field is empty or inaccessible
-
Inspect the executable path for unquoted spacesExamine the BINARY_PATH_NAME output from the previous step - check if the path contains spaces and is not enclosed in quotation marksAffected if The path contains one or more spaces and does not start and end with double quotes (e.g., C:\Program Files\SPICE\bin\spice.exe without quotes)
-
Identify intermediate directories in the unquoted pathIf the path is unquoted, parse each directory segment between the backslashes (e.g., for C:\Program Files\SPICE\bin\spice.exe, the intermediate directories are C:\Program and C:\Program Files\SPICE)Affected if Any intermediate directory in the path is writable by non-privileged users, increasing exploitation risk
You are affected if the SPICE service is installed and its executable path contains unquoted spaces with writable intermediate directories, allowing potential privilege escalation when the service starts.
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 dataQuote the SPICE service executable path in Windows service configuration to prevent path traversal exploitation, or ensure only trusted administrators can write to directories in the service path.
Fix this in Enterprise Virtualization
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2152 — 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-2013-2152 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