Directory Traversal Affecting libvirt-daemon-driver-storage-scsi package, versions <0:5.0.0-9.el7
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-ORACLE7-LIBVIRTDAEMONDRIVERSTORAGESCSI-2533033
- published 10 Apr 2022
- disclosed 2 Aug 2019
Introduced: 2 Aug 2019
CVE-2019-10168 Open this link in a new tabHow to fix?
Upgrade Oracle:7 libvirt-daemon-driver-storage-scsi to version 0:5.0.0-9.el7 or higher.
This issue was patched in ELSA-2019-4714.
NVD Description
Note: Versions mentioned in the description apply only to the upstream libvirt-daemon-driver-storage-scsi package and not the libvirt-daemon-driver-storage-scsi package as distributed by Oracle.
See How to fix? for Oracle:7 relevant fixed versions and status.
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
- https://linux.oracle.com/cve/CVE-2019-10168.html
- https://linux.oracle.com/errata/ELSA-2019-1579.html
- https://linux.oracle.com/errata/ELSA-2019-4714.html
- https://access.redhat.com/libvirt-privesc-vulnerabilities
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10168
- https://security.gentoo.org/glsa/202003-18