CVE-2019-10168
moderate-risk
Published 2019-08-02
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.
Do I need to act?
-
0.23% chance of exploitation
EPSS score — low exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
7
CVSS 7.8/10
High
LOCAL
/ LOW complexity
Affected Products (13)
Affected Vendors
References (6)
Vendor Advisory
https://access.redhat.com/libvirt-privesc-vulnerabilities
Issue Tracking
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10168
Third Party Advisory
https://security.gentoo.org/glsa/202003-18
Vendor Advisory
https://access.redhat.com/libvirt-privesc-vulnerabilities
Issue Tracking
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10168
Third Party Advisory
https://security.gentoo.org/glsa/202003-18
42
/ 100
moderate-risk
Severity
24/34 · High
Exploitability
1/34 · Minimal
Exposure
17/34 · Moderate