CVE-2013-4291 json
The virSecurityManagerSetProcessLabel function in libvirt 0.10.2.7, 1.0.5.5, and 1.1.1, when the domain has read an uid:gid label, does not…
published 13y ago modified 4mo ago also EUVD-2013-4187
- cvss
- 6.9
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 42%
- public exploits
- 0
- none known
Summary
The virSecurityManagerSetProcessLabel function in libvirt 0.10.2.7, 1.0.5.5, and 1.1.1, when the domain has read an uid:gid label, does not properly set group memberships, which allows local users to gain privileges.
Patch / fix
- libvirt Debian 14, Debian 13, Debian 12 1.1.2-2
debian advisories DEBIAN-CVE-2013-4291
Is CVE-2013-4291 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-4291 updated cvss 1.9
libvirt: supplementary groups not adjusted correctly when parsing label
-
Red Hat Enterprise Linux 5 libvirt Red Hat Enterprise Linux 6 libvirt, libvirt-client, libvirt-python, libvirt-lock-sanlock Red Hat Enterprise Linux 7 libvirt, libvirt-nss, libvirt-libs, libvirt-admin, libvirt-client, libvirt-daemon, +24 morenot affected: vulnerable code not present
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.49% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.9 | AV:L/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
References
Sources
- CVE List CVE-2013-4291
- NVD CVE-2013-4291
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.