CVE-2013-2151 json
Unquoted Windows search path vulnerability in Red Hat Enterprise Virtualization (RHEV) 3 and 3.2 allows local users to gain privileges via…
published 12y ago modified 4mo ago also EUVD-2013-2116
- cvss
- 7.2
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 36%
- public exploits
- 0
- none known
Summary
Unquoted Windows search path vulnerability in Red Hat Enterprise Virtualization (RHEV) 3 and 3.2 allows local users to gain privileges via a crafted application in an unspecified folder.
Patch / fix
- rhev-guest-tools-iso rhev manager 3 3.2-8
red hat advisories RHSA-2013:0925
Is CVE-2013-2151 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2013-2151 updated cvss 7.2
rhevm: rhev agent service unquoted search path
-
Red Hat Enterprise Virtualization 3 rhev-guest-toolsaffected: no fix planned “Will not fix”
-
Red Hat RHEV-M 3.2 rhev-guest-tools-iso 3.2-8fixed: vendor fix RHSA-2013:0925
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
References
-
rhn.redhat.com
/errata/RHSA-2013-0925.html
vendor-advisory
-
securityfocus.com
/bid/60473
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/84868
vdb-entry
Sources
- CVE List CVE-2013-2151
- NVD CVE-2013-2151
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.