The remote NewStart CGSL host, running version MAIN 4.05, has qemu-kvm packages installed that are affected by multiple vulnerabilities:

  - An out-of-bounds read access issue was found in the VGA     display emulator built into the Quick emulator (QEMU).
    It could occur while reading VGA memory to update     graphics display. A privileged user/process inside guest     could use this flaw to crash the QEMU process on the     host resulting in denial of service situation.
    (CVE-2017-13672)

  - An industry-wide issue was found in the way many modern     microprocessor designs have implemented speculative     execution of Load & Store instructions (a commonly used     performance optimization). It relies on the presence of     a precisely-defined instruction sequence in the     privileged code as well as the fact that memory read     from address to which a recent memory write has occurred     may see an older value and subsequently cause an update     into the microprocessor's data cache even for     speculatively executed instructions that never actually     commit (retire). As a result, an unprivileged attacker     could use this flaw to read privileged memory by     conducting targeted cache side-channel attacks.
    (CVE-2018-3639)

  - Quick Emulator (aka QEMU), when built with the Cirrus     CLGD 54xx VGA Emulator support, allows local guest OS     privileged users to cause a denial of service (out-of-     bounds access and QEMU process crash) by leveraging     incorrect region calculation when updating VGA display.
    (CVE-2018-7858)

  - An out-of-bounds read access issue was found in the VGA     emulator of QEMU. It could occur in vga_draw_text     routine, while updating display area for a vnc client. A     privileged user inside a guest could use this flaw to     crash the QEMU process resulting in DoS. (CVE-2018-5683)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

This update for xen fixes several issues. These security issues were fixed :

  - CVE-2017-5753, CVE-2017-5715, CVE-2017-5754: Prevent     information leaks via side effects of speculative     execution, aka 'Spectre' and 'Meltdown' attacks     (bsc#1074562, bsc#1068032)

  - CVE-2018-5683: The vga_draw_text function allowed local     OS guest privileged users to cause a denial of service     (out-of-bounds read and QEMU process crash) by     leveraging improper memory address validation     (bsc#1076116).

  - CVE-2017-18030: The cirrus_invalidate_region function     allowed local OS guest privileged users to cause a     denial of service (out-of-bounds array access and QEMU     process crash) via vectors related to negative pitch     (bsc#1076180).

  - CVE-2017-15595: x86 PV guest OS users were able to cause     a DoS (unbounded recursion, stack consumption, and     hypervisor crash) or possibly gain privileges via     crafted page-table stacking (bsc#1061081)

  - CVE-2017-17566: Prevent PV guest OS users to cause a     denial of service (host OS crash) or gain host OS     privileges in shadow mode by mapping a certain auxiliary     page (bsc#1070158).

  - CVE-2017-17563: Prevent guest OS users to cause a denial     of service (host OS crash) or gain host OS privileges by     leveraging an incorrect mask for reference-count     overflow checking in shadow mode (bsc#1070159).

  - CVE-2017-17564: Prevent guest OS users to cause a denial     of service (host OS crash) or gain host OS privileges by     leveraging incorrect error handling for reference     counting in shadow mode (bsc#1070160).

  - CVE-2017-17565: Prevent PV guest OS users to cause a     denial of service (host OS crash) if shadow mode and     log-dirty mode are in place, because of an incorrect     assertion related to M2P (bsc#1070163).

  - Added missing intermediate preemption checks for guest     requesting removal of memory. This allowed malicious     guest administrator to cause denial of service due to     the high cost of this operation (bsc#1080635).

  - Because of XEN not returning the proper error messages     when transitioning grant tables from v2 to v1 a     malicious guest was able to cause DoS or potentially     allowed for privilege escalation as well as information     leaks (bsc#1080662).

  - CVE-2017-5898: The CCID Card device emulator support was     vulnerable to an integer overflow flaw allowing a     privileged user to crash the Qemu process on the host     resulting in DoS (bsc#1024307)

  - Unprivileged domains could have issued well-timed writes     to xenstore which conflict with transactions to stall     progress of the control domain or driver domain,     possibly leading to DoS (bsc#1030144, XSA-206).

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

This update for qemu fixes the following issues: This update has the next round of Spectre v2 related patches, which now integrate with corresponding changes in libvirt. (CVE-2017-5715 bsc#1068032) The January 2018 release of qemu initially addressed the Spectre v2 vulnerability for KVM guests by exposing the spec-ctrl feature for all x86 vcpu types, which was the quick and dirty approach, but not the proper solution. We replaced our initial patch by the patches from upstream. This update defines spec_ctrl and ibpb cpu feature flags as well as new cpu models which are clones of existing models with either
-IBRS or -IBPB added to the end of the model name. These new vcpu models explicitly include the new feature(s), whereas the feature flags can be added to the cpu parameter as with other features. In short, for continued Spectre v2 protection, ensure that either the appropriate cpu feature flag is added to the QEMU command-line, or one of the new cpu models is used. Although migration from older versions is supported, the new cpu features won't be properly exposed to the guest until it is restarted with the cpu features explicitly added. A reboot is insufficient. A warning patch is added which attempts to detect a migration from a qemu version which had the quick and dirty fix (it only detects certain cases, but hopefully is helpful.) For additional information on Spectre v2 as it relates to QEMU, see:
https://www.qemu.org/2018/02/14/qemu-2-11-1-and-spectre-update/ A patch is added to continue to detect Spectre v2 mitigation features (as shown by cpuid), and if found provide that feature to guests, even if running on older KVM (kernel) versions which do not yet expose that feature to QEMU. (bsc#1082276) These two patches will be removed when we can reasonably assume everyone is running with the appropriate updates. Spectre fixes for IBM Z Series were included by providing more hw features to guests (bsc#1076813) Also security fixes for the following CVE issues are included :

  - CVE-2017-17381: The Virtio Vring implementation in QEMU     allowed local OS guest users to cause a denial of     service (divide-by-zero error and QEMU process crash) by     unsetting vring alignment while updating Virtio rings.
    (bsc#1071228)

  - CVE-2017-16845: The PS2 driver in Qemu did not validate     'rptr' and 'count' values during guest migration,     leading to out-of-bounds access. (bsc#1068613)

  - CVE-2017-15119: The Network Block Device (NBD) server in     Quick Emulator (QEMU), was vulnerable to a denial of     service issue. It could occur if a client sent large     option requests, making the server waste CPU time on     reading up to 4GB per request. A client could use this     flaw to keep the NBD server from serving other requests,     resulting in DoS. (bsc#1070144)

  - CVE-2017-18043: Integer overflow in the macro ROUND_UP     (n, d) in Quick Emulator (Qemu) allowed a user to cause     a denial of service (Qemu process crash). (bsc#1076775)

  - CVE-2018-5683: The VGA driver in Qemu allowed local OS     guest privileged users to cause a denial of service     (out-of-bounds read and QEMU process crash) by     leveraging improper memory address validation.
    (bsc#1076114)

  - CVE-2018-7550: The multiboot functionality in Quick     Emulator (aka QEMU) allowed local guest OS users to     execute arbitrary code on the QEMU host via an     out-of-bounds read or write memory access. (bsc#1083291)

  - CVE-2017-15124: VNC server implementation in Quick     Emulator (QEMU) was found to be vulnerable to an     unbounded memory allocation issue, as it did not     throttle the framebuffer updates sent to its client. If     the client did not consume these updates, VNC server     allocates growing memory to hold onto this data. A     malicious remote VNC client could use this flaw to cause     DoS to the server host. (bsc#1073489) Additional bugs     fixed :

  - Fix pcihp for 1.6 and older machine types (bsc#1074572)

  - Fix packaging dependencies (coreutils) for qemu-ksm     package (bsc#1040202)

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

This update for qemu fixes the following issues :

This update has the next round of Spectre v2 related patches, which now integrate with corresponding changes in libvirt. (CVE-2017-5715 bsc#1068032)

The January 2018 release of qemu initially addressed the Spectre v2 vulnerability for KVM guests by exposing the spec-ctrl feature for all x86 vcpu types, which was the quick and dirty approach, but not the proper solution.

We replaced our initial patch by the patches from upstream.

This update defines spec_ctrl and ibpb cpu feature flags as well as new cpu models which are clones of existing models with either -IBRS or -IBPB added to the end of the model name. These new vcpu models explicitly include the new feature(s), whereas the feature flags can be added to the cpu parameter as with other features. In short, for continued Spectre v2 protection, ensure that either the appropriate cpu feature flag is added to the QEMU command-line, or one of the new cpu models is used.

Although migration from older versions is supported, the new cpu features won't be properly exposed to the guest until it is restarted with the cpu features explicitly added. A reboot is insufficient.

A warning patch is added which attempts to detect a migration from a qemu version which had the quick and dirty fix (it only detects certain cases, but hopefully is helpful.) For additional information on Spectre v2 as it relates to QEMU, see:
https://www.qemu.org/2018/02/14/qemu-2-11-1-and-spectre-update/

A patch is added to continue to detect Spectre v2 mitigation features (as shown by cpuid), and if found provide that feature to guests, even if running on older KVM (kernel) versions which do not yet expose that feature to QEMU. (bsc#1082276)

These two patches will be removed when we can reasonably assume everyone is running with the appropriate updates.

Spectre fixes for IBM Z Series were included by providing more hw features to guests (bsc#1076813)

Also security fixes for the following CVE issues are included :

  - CVE-2017-17381: The Virtio Vring implementation in QEMU     allowed local OS guest users to cause a denial of     service (divide-by-zero error and QEMU process crash) by     unsetting vring alignment while updating Virtio rings.
    (bsc#1071228)

  - CVE-2017-16845: The PS2 driver in Qemu did not validate     'rptr' and 'count' values during guest migration,     leading to out-of-bounds access. (bsc#1068613)

  - CVE-2017-15119: The Network Block Device (NBD) server in     Quick Emulator (QEMU), was vulnerable to a denial of     service issue. It could occur if a client sent large     option requests, making the server waste CPU time on     reading up to 4GB per request. A client could use this     flaw to keep the NBD server from serving other requests,     resulting in DoS. (bsc#1070144)

  - CVE-2017-18043: Integer overflow in the macro ROUND_UP     (n, d) in Quick Emulator (Qemu) allowed a user to cause     a denial of service (Qemu process crash). (bsc#1076775)

  - CVE-2018-5683: The VGA driver in Qemu allowed local OS     guest privileged users to cause a denial of service     (out-of-bounds read and QEMU process crash) by     leveraging improper memory address validation.
    (bsc#1076114)

  - CVE-2018-7550: The multiboot functionality in Quick     Emulator (aka QEMU) allowed local guest OS users to     execute arbitrary code on the QEMU host via an     out-of-bounds read or write memory access. (bsc#1083291)

  - CVE-2017-15124: VNC server implementation in Quick     Emulator (QEMU) was found to be vulnerable to an     unbounded memory allocation issue, as it did not     throttle the framebuffer updates sent to its client. If     the client did not consume these updates, VNC server     allocates growing memory to hold onto this data. A     malicious remote VNC client could use this flaw to cause     DoS to the server host. (bsc#1073489)

Additional bugs fixed :

  - Fix pcihp for 1.6 and older machine types (bsc#1074572)

  - Fix packaging dependencies (coreutils) for qemu-ksm     package (bsc#1040202)

This update was imported from the SUSE:SLE-12-SP3:Update update project.

This update for xen fixes several issues. These security issues were fixed :

  - CVE-2017-5753, CVE-2017-5715, CVE-2017-5754: Prevent     information leaks via side effects of speculative     execution, aka 'Spectre' and 'Meltdown' attacks     (bsc#1074562, bsc#1068032)

  - CVE-2018-5683: The vga_draw_text function allowed local     OS guest privileged users to cause a denial of service     (out-of-bounds read and QEMU process crash) by     leveraging improper memory address validation     (bsc#1076116).

  - CVE-2017-18030: The cirrus_invalidate_region function     allowed local OS guest privileged users to cause a     denial of service (out-of-bounds array access and QEMU     process crash) via vectors related to negative pitch     (bsc#1076180).

  - CVE-2017-15595: x86 PV guest OS users were able to cause     a DoS (unbounded recursion, stack consumption, and     hypervisor crash) or possibly gain privileges via     crafted page-table stacking (bsc#1061081)

  - CVE-2017-17566: Prevent PV guest OS users to cause a     denial of service (host OS crash) or gain host OS     privileges in shadow mode by mapping a certain auxiliary     page (bsc#1070158).

  - CVE-2017-17563: Prevent guest OS users to cause a denial     of service (host OS crash) or gain host OS privileges by     leveraging an incorrect mask for reference-count     overflow checking in shadow mode (bsc#1070159).

  - CVE-2017-17564: Prevent guest OS users to cause a denial     of service (host OS crash) or gain host OS privileges by     leveraging incorrect error handling for reference     counting in shadow mode (bsc#1070160).

  - CVE-2017-17565: Prevent PV guest OS users to cause a     denial of service (host OS crash) if shadow mode and     log-dirty mode are in place, because of an incorrect     assertion related to M2P (bsc#1070163).

  - Added missing intermediate preemption checks for guest     requesting removal of memory. This allowed malicious     guest administrator to cause denial of service due to     the high cost of this operation (bsc#1080635).

  - Because of XEN not returning the proper error messages     when transitioning grant tables from v2 to v1 a     malicious guest was able to cause DoS or potentially     allowed for privilege escalation as well as information     leaks (bsc#1080662).

The update package also includes non-security fixes. See advisory for details.

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

USN-3575-1 fixed vulnerabilities in QEMU. The fix for CVE-2017-11334 caused a regression in Xen environments. This update removes the problematic fix pending further investigation.

We apologize for the inconvenience.

Original advisory details :

It was discovered that QEMU incorrectly handled guest ram. A privileged attacker inside the guest could use this issue to cause QEMU to crash, resulting in a denial of service. This issue only affected Ubuntu 14.04 LTS and Ubuntu 16.04 LTS. (CVE-2017-11334) David Buchanan discovered that QEMU incorrectly handled the VGA device. A privileged attacker inside the guest could use this issue to cause QEMU to crash, resulting in a denial of service. This issue was only addressed in Ubuntu 17.10. (CVE-2017-13672) Thomas Garnier discovered that QEMU incorrectly handled multiboot. An attacker could use this issue to cause QEMU to crash, resulting in a denial of service, or possibly execute arbitrary code on the host. In the default installation, when QEMU is used with libvirt, attackers would be isolated by the libvirt AppArmor profile. This issue only affected Ubuntu 14.04 LTS and Ubuntu 16.04 LTS. (CVE-2017-14167) Tuomas Tynkkynen discovered that QEMU incorrectly handled VirtFS directory sharing. An attacker could use this issue to obtain sensitive information from host memory. (CVE-2017-15038) Eric Blake discovered that QEMU incorrectly handled memory in the NBD server. An attacker could use this issue to cause the NBD server to crash, resulting in a denial of service. This issue only affected Ubuntu 17.10.
(CVE-2017-15118) Eric Blake discovered that QEMU incorrectly handled certain options to the NBD server. An attacker could use this issue to cause the NBD server to crash, resulting in a denial of service. This issue only affected Ubuntu 14.04 LTS and Ubuntu 16.04 LTS.
(CVE-2017-15119) Daniel Berrange discovered that QEMU incorrectly handled the VNC server. A remote attacker could possibly use this issue to consume memory, resulting in a denial of service. This issue was only addressed in Ubuntu 17.10. (CVE-2017-15124) Carl Brassey discovered that QEMU incorrectly handled certain websockets. A remote attacker could possibly use this issue to consume memory, resulting in a denial of service. This issue only affected Ubuntu 17.10.
(CVE-2017-15268) Guoxiang Niu discovered that QEMU incorrectly handled the Cirrus VGA device. A privileged attacker inside the guest could use this issue to cause QEMU to crash, resulting in a denial of service. (CVE-2017-15289) Cyrille Chatras discovered that QEMU incorrectly handled certain PS2 values during migration. An attacker could possibly use this issue to cause QEMU to crash, resulting in a denial of service, or possibly execute arbitrary code. This issue only affected Ubuntu 16.04 LTS and Ubuntu 17.10. (CVE-2017-16845) It was discovered that QEMU incorrectly handled the Virtio Vring implementation. An attacker could possibly use this issue to cause QEMU to crash, resulting in a denial of service. This issue only affected Ubuntu 16.04 LTS and Ubuntu 17.10. (CVE-2017-17381) Eric Blake discovered that QEMU incorrectly handled certain rounding operations. An attacker could possibly use this issue to cause QEMU to crash, resulting in a denial of service. This issue only affected Ubuntu 14.04 LTS and Ubuntu 16.04 LTS. (CVE-2017-18043) Jiang Xin and Lin ZheCheng discovered that QEMU incorrectly handled the VGA device.
A privileged attacker inside the guest could use this issue to cause QEMU to crash, resulting in a denial of service. (CVE-2018-5683).

Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

This update for kvm fixes the following issues :

  - This update has the next round of Spectre v2 related     patches, which now integrates with corresponding changes     in libvirt. A January 2018 release of qemu initially     addressed the Spectre v2 vulnerability for KVM guests by     exposing the spec-ctrl feature for all x86 vcpu types,     which was the quick and dirty approach, but not the     proper solution. We remove that initial patch and now     rely on patches from upstream. This update defines     spec_ctrl and ibpb cpu feature flags as well as new cpu     models which are clones of existing models with either
    -IBRS or -IBPB added to the end of the model name. These     new vcpu models explicitly include the new feature(s),     whereas the feature flags can be added to the cpu     parameter as with other features. In short, for     continued Spectre v2 protection, ensure that either the     appropriate cpu feature flag is added to the QEMU     command-line, or one of the new cpu models is used.
    Although migration from older versions is supported, the     new cpu features won't be properly exposed to the guest     until it is restarted with the cpu features explicitly     added. A reboot is insufficient.

  - A warning patch is added which attempts to detect a     migration from a qemu version which had the quick and     dirty fix (it only detects certain cases, but hopefully     is helpful.) For additional information on Spectre v2 as     it relates to QEMU, see:
    https://www.qemu.org/2018/02/14/qemu-2-11-1-and-spectre-     update/ (CVE-2017-5715 bsc#1068032)

  - A patch is added to continue to detect Spectre v2     mitigation features (as shown by cpuid), and if found     provide that feature to guests, even if running on older     KVM (kernel) versions which do not yet expose that     feature to QEMU. (bsc#1082276) These two patches will be     removed when we can reasonably assume everyone is     running with the appropriate updates.

  - Security fixes for the following CVE issues:
    (bsc#1076114 CVE-2018-5683) (bsc#1083291 CVE-2018-7550)

  - This patch is already included, add here for CVE track     (bsc#1076179 CVE-2017-18030)

  - Toolchain changes have cause the built size of     pxe-virtio.rom to exceed 64K. Tweak rarely used strings     in code to reduce size of the binary so it fits again.

  - Eliminate bogus use of CPUID_7_0_EDX_PRED_CMD which     we've carried since the initial Spectre v2 patch was     added. EDX bit 27 of CPUID Leaf 07H, Sub-leaf 0 provides     status on STIBP, and not the PRED_CMD MSR. Exposing the     STIBP CPUID feature bit to the guest is wrong in     general, since the VM doesn't directly control the     scheduling of physical hyperthreads. This is left     strictly to the L0 hypervisor.

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

According to the versions of the qemu-kvm packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

  - QEMU (aka Quick Emulator), when built with the VGA     display emulator support, allows local guest OS     privileged users to cause a denial of service     (out-of-bounds read and QEMU process crash) via vectors     involving display update.(CVE-2017-13672)

  - Use-after-free vulnerability in the sofree function in     slirp/socket.c in QEMU (aka Quick Emulator) allows     attackers to cause a denial of service (QEMU instance     crash) by leveraging failure to properly clear ifq_so     from pending packets.(CVE-2017-13711)

  - VNC server implementation in Quick Emulator (QEMU)     2.11.0 and older was found to be vulnerable to an     unbounded memory allocation issue, as it did not     throttle the framebuffer updates sent to its client. If     the client did not consume these updates, VNC server     allocates growing memory to hold onto this data. A     malicious remote VNC client could use this flaw to     cause DoS to the server host.(CVE-2017-15124)

  - Qemu through 2.10.0 allows remote attackers to cause a     memory leak by triggering slow data-channel read     operations, related to     io/channel-websock.c.(CVE-2017-15268)

  - The vga_draw_text function in Qemu allows local OS     guest privileged users to cause a denial of service     (out-of-bounds read and QEMU process crash) by     leveraging improper memory address     validation.(CVE-2018-5683)

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The remote Redhat Enterprise Linux 6 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2018:2162 advisory.

  - QEMU: vga: OOB read access during display update (CVE-2017-13672)

  - hw: cpu: speculative store bypass (CVE-2018-3639)

  - Qemu: Out-of-bounds read in vga_draw_text routine (CVE-2018-5683)

  - QEMU: cirrus: OOB access when updating VGA display (CVE-2018-7858)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

Security Fix(es) :

  - An industry-wide issue was found in the way many modern     microprocessor designs have implemented speculative     execution of Load &amp; Store instructions (a commonly     used performance optimization). It relies on the     presence of a precisely-defined instruction sequence in     the privileged code as well as the fact that memory read     from address to which a recent memory write has occurred     may see an older value and subsequently cause an update     into the microprocessor's data cache even for     speculatively executed instructions that never actually     commit (retire). As a result, an unprivileged attacker     could use this flaw to read privileged memory by     conducting targeted cache side-channel attacks.
    (CVE-2018-3639)

Note: This is the qemu-kvm side of the CVE-2018-3639 mitigation.

  - QEMU: cirrus: OOB access when updating VGA display     (CVE-2018-7858)

  - QEMU: vga: OOB read access during display update     (CVE-2017-13672)

  - Qemu: Out-of-bounds read in vga_draw_text routine     (CVE-2018-5683)

Several vulnerabilities were discovered in qemu, a fast processor emulator.

  - CVE-2017-15038     Tuomas Tynkkynen discovered an information leak in 9pfs.

  - CVE-2017-15119     Eric Blake discovered that the NBD server insufficiently     restricts large option requests, resulting in denial of     service.

  - CVE-2017-15124     Daniel Berrange discovered that the integrated VNC     server insufficiently restricted memory allocation,     which could result in denial of service.

  - CVE-2017-15268     A memory leak in websockets support may result in denial     of service.

  - CVE-2017-15289     Guoxiang Niu discovered an OOB write in the emulated     Cirrus graphics adaptor which could result in denial of     service.

  - CVE-2017-16845     Cyrille Chatras discovered an information leak in PS/2     mouse and keyboard emulation which could be exploited     during instance migration.

  - CVE-2017-17381     Dengzhan Heyuandong Bijunhua and Liweichao discovered     that an implementation error in the virtio vring     implementation could result in denial of service.

  - CVE-2017-18043     Eric Blake discovered an integer overflow in an     internally used macro which could result in denial of     service.

  - CVE-2018-5683     Jiang Xin and Lin ZheCheng discovered an OOB memory     access in the emulated VGA adaptor which could result in     denial of service.

  - CVE-2018-7550     Cyrille Chatras discovered that an OOB memory write when     using multiboot could result in the execution of     arbitrary code.

This update also backports a number of mitigations against the Spectre v2 vulnerability affecting modern CPUs (CVE-2017-5715 ). For additional information please refer to https://www.qemu.org/2018/01/04/spectre/

This update for qemu fixes the following issues: This update has the next round of Spectre v2 related patches, which now integrate with corresponding changes in libvirt. (CVE-2017-5715 bsc#1068032) The January 2018 release of qemu initially addressed the Spectre v2 vulnerability for KVM guests by exposing the spec-ctrl feature for all x86 vcpu types, which was the quick and dirty approach, but not the proper solution. We replaced our initial patch by the patches from upstream. This update defines spec_ctrl and ibpb cpu feature flags as well as new cpu models which are clones of existing models with either
-IBRS or -IBPB added to the end of the model name. These new vcpu models explicitly include the new feature(s), whereas the feature flags can be added to the cpu parameter as with other features. In short, for continued Spectre v2 protection, ensure that either the appropriate cpu feature flag is added to the QEMU command-line, or one of the new cpu models is used. Although migration from older versions is supported, the new cpu features won't be properly exposed to the guest until it is restarted with the cpu features explicitly added. A reboot is insufficient. A warning patch is added which attempts to detect a migration from a qemu version which had the quick and dirty fix (it only detects certain cases, but hopefully is helpful.) For additional information on Spectre v2 as it relates to QEMU, see:
https://www.qemu.org/2018/02/14/qemu-2-11-1-and-spectre-update/ A patch is added to continue to detect Spectre v2 mitigation features (as shown by cpuid), and if found provide that feature to guests, even if running on older KVM (kernel) versions which do not yet expose that feature to QEMU. (bsc#1082276) These two patches will be removed when we can reasonably assume everyone is running with the appropriate updates. Also security fixes for the following CVE issues are included :

  - CVE-2017-15119: The Network Block Device (NBD) server in     Quick Emulator (QEMU), was vulnerable to a denial of     service issue. It could occur if a client sent large     option requests, making the server waste CPU time on     reading up to 4GB per request. A client could use this     flaw to keep the NBD server from serving other requests,     resulting in DoS. (bsc#1070144)

  - CVE-2017-15124: VNC server implementation in Quick     Emulator (QEMU) was found to be vulnerable to an     unbounded memory allocation issue, as it did not     throttle the framebuffer updates sent to its client. If     the client did not consume these updates, VNC server     allocates growing memory to hold onto this data. A     malicious remote VNC client could use this flaw to cause     DoS to the server host. (bsc#1073489)

  - CVE-2017-16845: The PS2 driver in Qemu did not validate     'rptr' and 'count' values during guest migration,     leading to out-of-bounds access. (bsc#1068613)

  - CVE-2017-17381: The Virtio Vring implementation in QEMU     allowed local OS guest users to cause a denial of     service (divide-by-zero error and QEMU process crash) by     unsetting vring alignment while updating Virtio rings.
    (bsc#1071228)

  - CVE-2017-18030: A problem in the Cirrus driver in Qemu     allowed local OS guest privileged users to cause a     denial of service (out-of-bounds array access and QEMU     process crash) via vectors related to negative pitch.
    (bsc#1076179)

  - CVE-2017-18043: Integer overflow in the macro ROUND_UP     (n, d) in Quick Emulator (Qemu) allowed a user to cause     a denial of service (Qemu process crash). (bsc#1076775)

  - CVE-2018-5683: The VGA driver in Qemu allowed local OS     guest privileged users to cause a denial of service     (out-of-bounds read and QEMU process crash) by     leveraging improper memory address validation.
    (bsc#1076114)

  - CVE-2018-7550: The multiboot functionality in Quick     Emulator (aka QEMU) allowed local guest OS users to     execute arbitrary code on the QEMU host via an     out-of-bounds read or write memory access. (bsc#1083291)     Also the following bugs were fixed :

  - Eliminate bogus use of CPUID_7_0_EDX_PRED_CMD which     we've carried since the initial Spectre v2 patch was     added. EDX bit 27 of CPUID Leaf 07H, Sub-leaf 0 provides     status on STIBP, and not the PRED_CMD MSR. Exposing the     STIBP CPUID feature bit to the guest is wrong in     general, since the VM doesn't directly control the     scheduling of physical hyperthreads. This is left     strictly to the L0 hypervisor.

  - Spectre fixes for IBM Z series by providing more hw     features to guests (bsc#1076814)

  - Pre-add group kvm for qemu-tools (bsc#1040202)

  - the qemu-tools package also needs a prerequire of group     management tools, from the shadow package. (bsc#1085598)

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The remote Redhat Enterprise Linux 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2018:0816 advisory.

  - QEMU: vga: OOB read access during display update (CVE-2017-13672)

  - QEMU: Slirp: use-after-free when sending response (CVE-2017-13711)

  - Qemu: memory exhaustion through framebuffer update request message in VNC server (CVE-2017-15124)

  - QEMU: I/O: potential memory exhaustion via websock connection to VNC (CVE-2017-15268)

  - Qemu: Out-of-bounds read in vga_draw_text routine (CVE-2018-5683)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Oracle Linux 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2018-4289 advisory.

  - An out-of-bounds memory access issue was found in Quick Emulator (QEMU) before 1.7.2 in the VNC display     driver. This flaw could occur while refreshing the VNC display surface area in the     'vnc_refresh_server_surface'. A user inside a guest could use this flaw to crash the QEMU process.
    (CVE-2017-2633)

  - Integer overflow in the load_multiboot function in hw/i386/multiboot.c in QEMU (aka Quick Emulator) allows     local guest OS users to execute arbitrary code on the host via crafted multiboot header address values,     which trigger an out-of-bounds write. (CVE-2017-14167)

  - The mode4and5 write functions in hw/display/cirrus_vga.c in Qemu allow local OS guest privileged users to     cause a denial of service (out-of-bounds write access and Qemu process crash) via vectors related to dst     calculation. (CVE-2017-15289)

  - Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow     unauthorized disclosure of information to an attacker with local user access via a side-channel analysis.
    (CVE-2017-5715)

  - Systems with microprocessors utilizing speculative execution and branch prediction may allow unauthorized     disclosure of information to an attacker with local user access via a side-channel analysis.
    (CVE-2017-5753)

  - Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow     unauthorized disclosure of information to an attacker with local user access via a side-channel analysis     of the data cache. (CVE-2017-5754)

  - The vga_draw_text function in Qemu allows local OS guest privileged users to cause a denial of service     (out-of-bounds read and QEMU process crash) by leveraging improper memory address validation.
    (CVE-2018-5683)

  - QEMU (aka Quick Emulator), when built with the VGA display emulator support, allows local guest OS     privileged users to cause a denial of service (out-of-bounds read and QEMU process crash) via vectors     involving display update. (CVE-2017-13672)

  - Use-after-free vulnerability in the sofree function in slirp/socket.c in QEMU (aka Quick Emulator) allows     attackers to cause a denial of service (QEMU instance crash) by leveraging failure to properly clear     ifq_so from pending packets. (CVE-2017-13711)

  - VNC server implementation in Quick Emulator (QEMU) 2.11.0 and older was found to be vulnerable to an     unbounded memory allocation issue, as it did not throttle the framebuffer updates sent to its client. If     the client did not consume these updates, VNC server allocates growing memory to hold onto this data. A     malicious remote VNC client could use this flaw to cause DoS to the server host. (CVE-2017-15124)

  - Qemu through 2.10.0 allows remote attackers to cause a memory leak by triggering slow data-channel read     operations, related to io/channel-websock.c. (CVE-2017-15268)

  - Quick Emulator (aka QEMU), when built with the Cirrus CLGD 54xx VGA Emulator support, allows local guest     OS privileged users to cause a denial of service (out-of-bounds access and QEMU process crash) by     leveraging incorrect region calculation when updating VGA display. (CVE-2018-7858)

  - Systems with microprocessors utilizing speculative execution and speculative execution of memory reads     before the addresses of all prior memory writes are known may allow unauthorized disclosure of information     to an attacker with local user access via a side-channel analysis, aka Speculative Store Bypass (SSB),     Variant 4. (CVE-2018-3639)

  - The load_multiboot function in hw/i386/multiboot.c in Quick Emulator (aka QEMU) allows local guest OS     users to execute arbitrary code on the QEMU host via a mh_load_end_addr value greater than     mh_bss_end_addr, which triggers an out-of-bounds read or write memory access. (CVE-2018-7550)

  - m_cat in slirp/mbuf.c in Qemu has a heap-based buffer overflow via incoming fragmented datagrams.
    (CVE-2018-11806)

  - qmp_guest_file_read in qga/commands-posix.c and qga/commands-win32.c in qemu-ga (aka QEMU Guest Agent) in     QEMU 2.12.50 has an integer overflow causing a g_malloc0() call to trigger a segmentation fault when     trying to allocate a large memory chunk. The vulnerability can be exploited by sending a crafted QMP     command (including guest-file-read with a large count value) to the agent via the listening socket.
    (CVE-2018-12617)

  - Quick Emulator (Qemu) built with the VirtFS, host directory sharing via Plan 9 File System (9pfs) support,     is vulnerable to an improper access control issue. It could occur while accessing files on a shared host     directory. A privileged user inside guest could use this flaw to access host file system beyond the shared     folder and potentially escalating their privileges on a host. (CVE-2017-7471)

  - A stack buffer overflow flaw was found in the Quick Emulator (QEMU) before 2.9 built with the Network     Block Device (NBD) client support. The flaw could occur while processing server's response to a     'NBD_OPT_LIST' request. A malicious NBD server could use this issue to crash a remote NBD client resulting     in DoS or potentially execute arbitrary code on client host with privileges of the QEMU process.
    (CVE-2017-2630)

  - Stack-based buffer overflow in hw/usb/redirect.c in QEMU (aka Quick Emulator) allows local guest OS users     to cause a denial of service (QEMU process crash) via vectors related to logging debug messages.
    (CVE-2017-10806)

  - The address_space_write_continue function in exec.c in QEMU (aka Quick Emulator) allows local guest OS     privileged users to cause a denial of service (out-of-bounds access and guest instance crash) by     leveraging use of qemu_map_ram_ptr to access guest ram block area. (CVE-2017-11334)

  - The Virtio Vring implementation in QEMU allows local OS guest users to cause a denial of service (divide-     by-zero error and QEMU process crash) by unsetting vring alignment while updating Virtio rings.
    (CVE-2017-17381)

  - Quick Emulator (Qemu) built with the VirtFS, host directory sharing via Plan 9 File System(9pfs) support,     is vulnerable to an improper access control issue. It could occur while accessing virtfs metadata files in     mapped-file security mode. A guest user could use this flaw to escalate their privileges inside guest.
    (CVE-2017-7493)

  - hw/scsi/vmw_pvscsi.c in QEMU (aka Quick Emulator) allows local guest OS privileged users to cause a denial     of service (infinite loop and CPU consumption) via the message ring page count. (CVE-2017-8112)

  - QEMU (aka Quick Emulator), when built with MegaRAID SAS 8708EM2 Host Bus Adapter emulation support, allows     local guest OS privileged users to cause a denial of service (NULL pointer dereference and QEMU process     crash) via vectors involving megasas command processing. (CVE-2017-9503)

  - QEMU (aka Quick Emulator), when built with the IDE disk and CD/DVD-ROM Emulator support, allows local     guest OS privileged users to cause a denial of service (NULL pointer dereference and QEMU process crash)     by flushing an empty CDROM device drive. (CVE-2017-12809)

  - Race condition in the v9fs_xattrwalk function in hw/9pfs/9p.c in QEMU (aka Quick Emulator) allows local     guest OS users to obtain sensitive information from host heap memory via vectors related to reading     extended attributes. (CVE-2017-15038)

  - The Network Block Device (NBD) server in Quick Emulator (QEMU) before 2.11 is vulnerable to a denial of     service issue. It could occur if a client sent large option requests, making the server waste CPU time on     reading up to 4GB per request. A client could use this flaw to keep the NBD server from serving other     requests, resulting in DoS. (CVE-2017-15119)

  - hw/input/ps2.c in Qemu does not validate 'rptr' and 'count' values during guest migration, leading to out-     of-bounds access. (CVE-2017-16845)

  - The cirrus_invalidate_region function in hw/display/cirrus_vga.c in Qemu allows local OS guest privileged     users to cause a denial of service (out-of-bounds array access and QEMU process crash) via vectors related     to negative pitch. (CVE-2017-18030)

  - Integer overflow in the macro ROUND_UP (n, d) in Quick Emulator (Qemu) allows a user to cause a denial of     service (Qemu process crash). (CVE-2017-18043)

  - Memory leak in the audio/audio.c in QEMU (aka Quick Emulator) allows remote attackers to cause a denial of     service (memory consumption) by repeatedly starting and stopping audio capture. (CVE-2017-8309)

  - Memory leak in the keyboard input event handlers support in QEMU (aka Quick Emulator) allows local guest     OS privileged users to cause a denial of service (host memory consumption) by rapidly generating large     keyboard events. (CVE-2017-8379)

  - Buffer overflow in the megasas_mmio_write function in Qemu 2.9.0 allows remote attackers to have     unspecified impact via unknown vectors. (CVE-2017-8380)

  - The vga display update in mis-calculated the region for the dirty bitmap snapshot in case split screen     mode is used causing a denial of service (assertion failure) in the cpu_physical_memory_snapshot_get_dirty     function. (CVE-2017-13673)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Redhat Enterprise Linux 5 host has one or more packages installed that are affected by multiple vulnerabilities that have been acknowledged by the vendor but will not be patched.

  - xsa224 xen: grant table operations mishandle reference counts (XSA-224) (CVE-2017-10921)

  - The qemu implementation in libvirt before 1.3.0 and Xen allows local guest OS users to cause a denial of     service (host disk consumption) by writing to stdout or stderr. (CVE-2014-3672)

  - Heap-based buffer overflow in the PCNET controller in QEMU allows remote attackers to execute arbitrary     code by sending a packet with TXSTATUS_STARTPACKET set and then a crafted packet with TXSTATUS_DEVICEOWNS     set. (CVE-2015-3209)

Note that Nessus has not tested for these issues but has instead relied on the package manager's report that the package is installed.

ID	名稱	產品	系列	已發布	已更新	嚴重性
127389	NewStart CGSL MAIN 4.05 : qemu-kvm Multiple Vulnerabilities (NS-SA-2019-0133)	Nessus	NewStart CGSL Local Security Checks	2019/8/12	2021/4/15	medium
108369	SUSE SLES11 Security Update : xen (SUSE-SU-2018:0678-1) (Meltdown) (Spectre)	Nessus	SuSE Local Security Checks	2018/3/15	2021/1/19	high
108533	SUSE SLED12 / SLES12 Security Update : qemu (SUSE-SU-2018:0762-1) (Spectre)	Nessus	SuSE Local Security Checks	2018/3/22	2021/1/13	critical
108576	openSUSE Security Update : qemu (openSUSE-2018-291) (Spectre)	Nessus	SuSE Local Security Checks	2018/3/23	2021/1/19	critical
107144	SUSE SLES12 Security Update : xen (SUSE-SU-2018:0609-1) (Meltdown) (Spectre)	Nessus	SuSE Local Security Checks	2018/3/6	2019/9/10	high
107145	Ubuntu 14.04 LTS / 16.04 LTS : QEMU regression (USN-3575-2)	Nessus	Ubuntu Local Security Checks	2018/3/6	2023/10/20	critical
109358	SUSE SLES11 Security Update : kvm (SUSE-SU-2018:1077-1) (Spectre)	Nessus	SuSE Local Security Checks	2018/4/26	2021/1/19	high
109511	EulerOS 2.0 SP2 : qemu-kvm (EulerOS-SA-2018-1113)	Nessus	Huawei Local Security Checks	2018/5/2	2021/1/6	high
111000	RHEL 6 : qemu-kvm (RHSA-2018:2162)	Nessus	Red Hat Local Security Checks	2018/7/11	2024/4/27	medium
111003	Scientific Linux Security Update : qemu-kvm on SL6.x i386/x86_64 (20180710) (Spectre)	Nessus	Scientific Linux Local Security Checks	2018/7/11	2021/4/15	medium
110208	Debian DSA-4213-1 : qemu - security update (Spectre)	Nessus	Debian Local Security Checks	2018/5/30	2020/9/11	critical
108686	SUSE SLED12 / SLES12 Security Update : qemu (SUSE-SU-2018:0831-1) (Spectre)	Nessus	SuSE Local Security Checks	2018/3/28	2021/1/13	critical
108986	RHEL 7 : qemu-kvm (RHSA-2018:0816)	Nessus	Red Hat Local Security Checks	2018/4/11	2024/4/27	high
180858	Oracle Linux 7 : qemu (ELSA-2018-4289)	Nessus	Oracle Linux Local Security Checks	2023/9/7	2023/9/8	critical
199537	RHEL 5 : xen (Unpatched Vulnerability)	Nessus	Red Hat Local Security Checks	2024/6/3	2024/6/3	critical

偵測

搜尋 Plugin

medium

high

critical

critical

high

critical

high

high

medium

medium

critical

critical

high

critical

critical