Description
The virConnectBaselineHypervisorCPU() and virConnectCompareHypervisorCPU() libvirt APIs, 4.x.x before 4.10.1 and 5.x.x before 5.4.1, accept an "emulator" argument to specify the program providing emulation for a domain. Since v1.2.19, libvirt will execute that program to probe the domain's capabilities. Read-only clients could specify an arbitrary path for this argument, causing libvirtd to execute a crafted executable with its own privileges.
Metrics
CVSS 3.1 7.8/10
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| libvirt | libvirt | 4.x.x before 4.10.1; 5.x.x before 5.4.1 |
References
- https://access.redhat.com/libvirt-privesc-vulnerabilitiesVendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10168Issue Tracking, Third Party Advisory, Vendor Advisory
- https://security.gentoo.org/glsa/202003-18Third Party Advisory
- https://access.redhat.com/libvirt-privesc-vulnerabilitiesVendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10168Issue Tracking, Third Party Advisory, Vendor Advisory
- https://security.gentoo.org/glsa/202003-18Third Party Advisory
Timeline
- Published
- Aug 2, 2019
- Last modified
- Jun 17, 2026
- NVD status
- Modified