CVE-2019-10168: Path Traversal
Last updated 24 July 2024
Other sources
The virConnectBaselineHypervisorCPU() and virConnectCompareHypervisorCPU() libvirt APIs 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.
— Red Hat
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.
Affected Software
Remediation
Information
Event History
Parent advisories
This vulnerability appears in the following advisories.
Frequently Asked Questions
What is CVE-2019-10168?
CVE-2019-10168 is a vulnerability that affects the virConnectBaselineHypervisorCPU() and virConnectCompareHypervisorCPU() libvirt APIs.
What is the severity of CVE-2019-10168?
CVE-2019-10168 has a severity value of 8.8, which is considered high.
Which versions of libvirt are affected by CVE-2019-10168?
Versions 4.x.x before 4.10.1 and 5.x.x before 5.4.1 of libvirt are affected by CVE-2019-10168.
How can I fix CVE-2019-10168?
To fix CVE-2019-10168, update libvirt to version 4.10.1 or 5.4.1, depending on the version you are using.
Where can I find more information about CVE-2019-10168?
You can find more information about CVE-2019-10168 at the following references: [1](https://access.redhat.com/libvirt-privesc-vulnerabilities), [2](https://libvirt.org/git/?p=libvirt.git;a=commit;h=bf6c2830b6c338b1f5699b095df36f374777b291), [3](https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1722466).