REDHAT-BUG-476560
First published: Mon Dec 15 2008(Updated: )
Daniel Berrange discovered that libvirt fails to check whether connection to libvirtd is in read-only or read-write mode, possibly allowing non-privileged users with access to the host machine to perform certain actions that should be restricted to administrative users only. The following methods in libvirt.c are missing a check against the read-only connection flag: virDomainMigrate virDomainMigratePrepare virDomainMigratePerform virDomainMigrateFinish virDomainMigratePrepare2 virDomainMigrateFinish2 virDomainBlockPeek virDomainMemoryPeek virDomainSetAutostart virNetworkSetAutostart virConnectFindStoragePoolSources virStoragePoolSetAutostart In recent versions, libvirt uses PolicyKit to authorize connections from users. Default policy allows any local user to connect in the read-only mode. Older versions of libvirt, or version not compiled with PolicyKit or with PolicyKit authorization disabled, default to allow read-only connections to all local users. Thus out of the box unprivileged local users may be able to migrate VMs, set or unset the autostart flag for domains, networks & storage pools, and access privileged data in the VM memory, or disks. All TCP remote connections are read-write, and fully authenticated, thus not impacted.
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Oracle Libvirt | <=older versions=policyKit-compiled versions |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://bugzilla.redhat.com/show_bug.cgi/attachment.cgi?id=326995&action=diff
- https://bugzilla.redhat.com/show_bug.cgi/attachment.cgi?id=326995&action=edit
- https://www.redhat.com/archives/libvir-list/2008-December/msg00522.html
- http://git.et.redhat.com/?p=libvirt.git;a=commitdiff;h=e87a5440dff8020d7247656368023e1b2d57415c
- https://rhn.redhat.com/errata/RHSA-2009-0382.html
- http://rhn.redhat.com/errata/RHSA-2009-0382.html
- https://admin.fedoraproject.org/updates/F10/FEDORA-2008-11443
- https://admin.fedoraproject.org/updates/F9/FEDORA-2008-11433
- https://bugzilla.redhat.com/show_bug.cgi?id=476560
Frequently Asked Questions
What is the severity of REDHAT-BUG-476560?
The severity of REDHAT-BUG-476560 is considered critical due to the potential for unauthorized access to privileged actions.
How do I fix REDHAT-BUG-476560?
To fix REDHAT-BUG-476560, you should update libvirt to the latest patched version that addresses the security issue.
Who is affected by REDHAT-BUG-476560?
Users of older versions of libvirt and policyKit-compiled versions are affected by REDHAT-BUG-476560.
What actions can be performed due to REDHAT-BUG-476560?
Due to REDHAT-BUG-476560, non-privileged users may perform administrative actions that should be restricted.
What is libvirt in context of REDHAT-BUG-476560?
Libvirt is an API, daemon, and management tool for managing platform virtualization, which is vulnerable in this case.
- agent/type
- agent/first-publish-date
- agent/last-modified-date
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2008-5086
- agent/references
- agent/severity
- agent/description
- agent/event
- agent/trending
- agent/source
- agent/softwarecombine
- agent/tags
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/libvirt
- canonical/oracle libvirt