最佳答案shuguet
\nBut what I can tell you is that the version of libvirt deployed on the CVM does not seems to be impacted.\nThe CVEs you mention and the Libvirt advisories both refers to versions 1.0.1 or later of libvirt.
\n
\nBut the CVMs (as of the latest publicly available release, 3.5.3.1) uses the version 0.10.2:
\nnutanix@cvm$ ls -la \/usr\/lib64\/libvirt.so.0lrwxrwxrwx. 1 root root 17 Apr 3 15:14 \/usr\/lib64\/libvirt.so.0 -> libvirt.so.0.10.2<\/b>
\nnutanix@cvm$ virsh --version=longVirsh command line tool of libvirt 0.10.2<\/b>See web site at http:\/\/libvirt.org\/
\nCompiled with support for:Hypervisors: QEMU\/KVM LXC ESX TestNetworking: Remote Network Bridging Interface netcf Nwfilter VirtualPortStorage: Dir Disk Filesystem SCSI Multipath iSCSI LVMMiscellaneous: Daemon Nodedev SELinux Secrets Debug DTrace Readline
\n
\nEdit: There is a dormant flaw starting at version 0.0.5, and activated after 0.7.5, that may allow denial of service. But the major threat is the privileged information disclosure, and that is only after version 1.0.0.
\nIn any case, both flaws can only be activated via local access to the Nutanix configuration.
\n
\nSylvain.","className":"post__content__best_answer"}">