CVE-2013-4291: Medium severity red hat libvirt-daemon-driver-storage-iscsi-direct vulnerability
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.
Other sources
Upstream Commit 29fe5d7 (released in 1.1.1) introduced a latent problem for any caller of virSecurityManagerSetProcessLabel and where the domain already had a uid:gid label to be parsed. Such a setup would collect the list of supplementary groups during virSecurityManagerPreFork, but then ignores that information, and thus fails to call setgroups() to adjust the supplementary groups of the process.
Introduced by: http://libvirt.org/git/?p=libvirt.git;a=commit;h=29fe5d745fbe207ec2415441d4807ae76be05974
Upstream fix: http://libvirt.org/git/?p=libvirt.git;a=commit;h=fe11d34a6d46d6641ce90dc665164fda7bb6bff8
— Red Hat
Affected Software
Remediation
Patch Available
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2013-4291?
CVE-2013-4291 is considered a high-severity vulnerability due to its potential to allow local users to gain elevated privileges.
How do I fix CVE-2013-4291?
To mitigate CVE-2013-4291, upgrade to libvirt versions 1.1.2 or later that address this vulnerability.
What versions of libvirt are affected by CVE-2013-4291?
CVE-2013-4291 affects libvirt versions 0.10.2.7, 1.0.5.5, and 1.1.1.
What is the root cause of CVE-2013-4291?
The root cause of CVE-2013-4291 is improper handling of group memberships in the virSecurityManagerSetProcessLabel function.
Can CVE-2013-4291 be exploited remotely?
CVE-2013-4291 cannot be exploited remotely as it requires local access to the system.