Directory Traversal Affecting libvirt package, versions <0:4.5.0-10.amzn2.12.1


Severity

Recommended
0.0
high
0
10

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.55% (42nd percentile)

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 IDSNYK-AMZN2-LIBVIRT-1673162
  • published27 Sept 2021
  • disclosed2 Aug 2019

Introduced: 2 Aug 2019

CVE-2019-10168  (opens in a new tab)
CWE-22  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2 libvirt to version 0:4.5.0-10.amzn2.12.1 or higher.
This issue was patched in ALAS2-2019-1274.

NVD Description

Note: Versions mentioned in the description apply only to the upstream libvirt package and not the libvirt package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2 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.

CVSS Base Scores

version 3.1