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 |
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Information
Published : 2019-08-02 06:15
Updated : 2020-10-15 06:28
NVD link : CVE-2019-10168
Mitre link : CVE-2019-10168
JSON object : View
CWE
CWE-22
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Products Affected
redhat
- enterprise_linux_desktop
- enterprise_linux
- enterprise_linux_workstation
- virtualization
- enterprise_linux_server_aus
- libvirt
- enterprise_linux_server_tus
- enterprise_linux_server_eus
- enterprise_linux_server