It was discovered that libvirtd before versions 4.10.1 and 5.4.1 would permit read-only clients to use the virDomainSaveImageGetXMLDesc() API, specifying an arbitrary path which would be accessed with the permissions of the libvirtd process. An attacker with access to the libvirtd socket could use this to probe the existence of arbitrary files, cause denial of service or cause libvirtd to execute arbitrary programs.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
| Link | Tags |
|---|---|
| https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10161 | issue tracking third party advisory patch |
| https://access.redhat.com/libvirt-privesc-vulnerabilities | third party advisory |
| https://libvirt.org/git/?p=libvirt.git%3Ba=commit%3Bh=aed6a032cead4386472afb24b16196579e239580 | |
| https://usn.ubuntu.com/4047-2/ | third party advisory vendor advisory |
| https://security.gentoo.org/glsa/202003-18 | third party advisory vendor advisory |