First published: Tue Sep 10 2013(Updated: )
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: <a href="http://libvirt.org/git/?p=libvirt.git;a=commit;h=29fe5d745fbe207ec2415441d4807ae76be05974">http://libvirt.org/git/?p=libvirt.git;a=commit;h=29fe5d745fbe207ec2415441d4807ae76be05974</a> Upstream fix: <a href="http://libvirt.org/git/?p=libvirt.git;a=commit;h=fe11d34a6d46d6641ce90dc665164fda7bb6bff8">http://libvirt.org/git/?p=libvirt.git;a=commit;h=fe11d34a6d46d6641ce90dc665164fda7bb6bff8</a>
Affected Software | Affected Version | How to fix |
---|---|---|
libvirt |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-1006509 is categorized as medium due to the risk of improper security labeling.
To fix REDHAT-BUG-1006509, you should update to a version of libvirt that includes the upstream commits addressing this issue.
REDHAT-BUG-1006509 affects systems using libvirt where there are uid:gid labels set for domains.
Symptoms of REDHAT-BUG-1006509 may include failure to correctly apply security labels to processes.
Currently, there are no established workarounds for REDHAT-BUG-1006509 other than applying the required updates.