It was discovered that libvirtd, versions 4.x.x before 4.10.1 and 5.x.x before 5.4.1, would permit readonly clients to use the virDomainManagedSaveDefineXML() API, which would permit them to modify managed save state files. If a managed save had already been created by a privileged user, a local attacker could modify this file such that libvirtd would execute an arbitrary program when the domain was resumed.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Libvirt | Redhat | 4.0.0 (including) | 4.10.1 (excluding) |
| Libvirt | Redhat | 5.0.0 (including) | 5.4.1 (excluding) |
| Red Hat Enterprise Linux 7 | RedHat | libvirt-0:4.5.0-10.el7_6.12 | * |
| Red Hat Enterprise Linux 8 | RedHat | virt:rhel-8000020190618154454.f8e95b4e | * |
| Red Hat Enterprise Linux 8 Advanced Virtualization | RedHat | virt:8.0.0-8000020190620145550.f8e95b4e | * |
| Red Hat Virtualization 4 for Red Hat Enterprise Linux 7 | RedHat | redhat-release-virtualization-host-0:4.3.4-1.el7ev | * |
| Red Hat Virtualization 4 for Red Hat Enterprise Linux 7 | RedHat | redhat-virtualization-host-0:4.3.4-20190620.3.el7_6 | * |
| Libvirt | Ubuntu | bionic | * |
| Libvirt | Ubuntu | cosmic | * |
| Libvirt | Ubuntu | devel | * |
| Libvirt | Ubuntu | disco | * |
| Libvirt | Ubuntu | trusty | * |
Access control involves the use of several protection mechanisms such as:
When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses: