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.
References
Link | Resource |
---|---|
https://access.redhat.com/libvirt-privesc-vulnerabilities | Vendor Advisory |
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10168 | Issue Tracking Third Party Advisory Vendor Advisory |
https://security.gentoo.org/glsa/202003-18 | Third Party Advisory |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: redhat
Published: 2019-08-02T12:08:14
Updated: 2020-03-15T04:06:03
Reserved: 2019-03-27T00:00:00
Link: CVE-2019-10168
JSON object: View
NVD Information
Status : Analyzed
Published: 2019-08-02T13:15:12.247
Modified: 2020-10-15T13:28:10.487
Link: CVE-2019-10168
JSON object: View
Redhat Information
No data.