Enterprise VirtualizationApplication · Redhat
CVE-2013-2176
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 Red Hat Enterprise Virtualization Application Provisioning Tool (RHEV-APT) in the rhev-guest-tools-iso package 3.2 allows local users to gain privileges via a Trojan horse application.
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 confidenceUnquoted Windows service path vulnerability in RHEV-APT allows local privilege escalation. When service executable paths contain spaces without quotes, Windows searches and executes programs in intermediate directories left-to-right, enabling attackers to plant Trojan horse executables.
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.0= 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.
-
Determine if RHEV-APT is installedCheck the Windows registry or program files for RHEV-APT installation: Review installed programs in Add/Remove Programs, or check for RHEV-APT executable in C:\Program Files\ or C:\Program Files (x86)\, or query the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for RHEV-APT entriesAffected if RHEV-APT is not installed on the system
-
Locate the RHEV-APT Windows serviceOpen Windows Services console (services.msc) or run 'sc queryex type= service state= all' to list all services, then search for a service related to RHEV-APT or Red Hat VirtualizationAffected if No RHEV-APT related Windows service is found
-
Inspect the service executable pathRun 'sc qc <service_name>' to query the service configuration, or use 'wmic service where "name='<service_name>'" get PathName' to retrieve the executable path; alternatively, right-click the service in services.msc and check the 'Path to executable' fieldAffected if The displayed path contains spaces and is not enclosed in quotation marks (e.g., C:\Program Files\RHEV\apt\rhev-apt.exe instead of "C:\Program Files\RHEV\apt\rhev-apt.exe")
-
Verify path contains exploitable spacesExamine the executable path returned from the previous step; identify if any directory names in the path contain spaces (e.g., 'Program Files', 'Red Hat') and confirm the path is not wrapped in quotesAffected if The service path has spaces in directory names and is unquoted
A user is affected if RHEV-APT is installed as a Windows service with an unquoted executable path containing spaces, allowing privilege escalation through Trojan horse program injection in intermediate directories.
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 dataFix the unquoted service path by either quoting the executable path in the service configuration or removing spaces from directory names in the path.
Fix this in Enterprise Virtualization
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2176 — 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-2176 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