xen/arm: Boot modules are not scrubbed The bootloader will load boot modules (e.g. kernel, initramfs...) in a temporary area before they are copied by Xen to each domain memory. To ensure sensitive data is not leaked from the modules, Xen must "scrub" them before handing the page over to the allocator. Unfortunately, it was discovered that modules will not be scrubbed on Arm.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - xen/arm: Boot modules are not scrubbed The bootloader will load boot modules (e.g. kernel, initramfs...)     in a temporary area before they are copied by Xen to each domain memory. To ensure sensitive data is not     leaked from the modules, Xen must scrub them before handing the page over to the allocator.
    Unfortunately, it was discovered that modules will not be scrubbed on Arm. (CVE-2021-28693)

Note that Nessus relies on the presence of the package as reported by the vendor.

There are packages installed that are affected by multiple vulnerabilities referenced in the following CVEs:

  - Observable response discrepancy in some Intel(R) Processors may allow an authorized user to potentially
    enable information disclosure via local access. (CVE-2021-0089)

  - An issue was discovered in Xen 4.9 through 4.14.x. On Arm, a guest is allowed to control whether memory
    accesses are bypassing the cache. This means that Xen needs to ensure that all writes (such as the ones
    during scrubbing) have reached the memory before handing over the page to a guest. Unfortunately, the
    operation to clean the cache is happening before checking if the page was scrubbed. Therefore there is no
    guarantee when all the writes will reach the memory. (CVE-2021-26933)

  - x86: TSX Async Abort protections not restored after S3 This issue relates to the TSX Async Abort
    speculative security vulnerability. Please see https://xenbits.xen.org/xsa/advisory-305.html for details.
    Mitigating TAA by disabling TSX (the default and preferred option) requires selecting a non-default
    setting in MSR_TSX_CTRL. This setting isn't restored after S3 suspend. (CVE-2021-28690)

  - inappropriate x86 IOMMU timeout detection / handling IOMMUs process commands issued to them in parallel
    with the operation of the CPU(s) issuing such commands. In the current implementation in Xen, asynchronous
    notification of the completion of such commands is not used. Instead, the issuing CPU spin-waits for the
    completion of the most recently issued command(s). Some of these waiting loops try to apply a timeout to
    fail overly-slow commands. The course of action upon a perceived timeout actually being detected is
    inappropriate: - on Intel hardware guests which did not originally cause the timeout may be marked as
    crashed, - on AMD hardware higher layer callers would not be notified of the issue, making them continue
    as if the IOMMU operation succeeded. (CVE-2021-28692)

  - xen/arm: Boot modules are not scrubbed The bootloader will load boot modules (e.g. kernel, initramfs...)
    in a temporary area before they are copied by Xen to each domain memory. To ensure sensitive data is not
    leaked from the modules, Xen must "scrub" them before handing the page over to the allocator.
    Unfortunately, it was discovered that modules will not be scrubbed on Arm. (CVE-2021-28693)

There are packages installed that are affected by multiple vulnerabilities referenced in the following CVEs:

  - Observable response discrepancy in some Intel(R) Processors may allow an authorized user to potentially
    enable information disclosure via local access. (CVE-2021-0089)

  - x86: TSX Async Abort protections not restored after S3 This issue relates to the TSX Async Abort
    speculative security vulnerability. Please see https://xenbits.xen.org/xsa/advisory-305.html for details.
    Mitigating TAA by disabling TSX (the default and preferred option) requires selecting a non-default
    setting in MSR_TSX_CTRL. This setting isn't restored after S3 suspend. (CVE-2021-28690)

  - inappropriate x86 IOMMU timeout detection / handling IOMMUs process commands issued to them in parallel
    with the operation of the CPU(s) issuing such commands. In the current implementation in Xen, asynchronous
    notification of the completion of such commands is not used. Instead, the issuing CPU spin-waits for the
    completion of the most recently issued command(s). Some of these waiting loops try to apply a timeout to
    fail overly-slow commands. The course of action upon a perceived timeout actually being detected is
    inappropriate: - on Intel hardware guests which did not originally cause the timeout may be marked as
    crashed, - on AMD hardware higher layer callers would not be notified of the issue, making them continue
    as if the IOMMU operation succeeded. (CVE-2021-28692)

  - xen/arm: Boot modules are not scrubbed The bootloader will load boot modules (e.g. kernel, initramfs...)
    in a temporary area before they are copied by Xen to each domain memory. To ensure sensitive data is not
    leaked from the modules, Xen must "scrub" them before handing the page over to the allocator.
    Unfortunately, it was discovered that modules will not be scrubbed on Arm. (CVE-2021-28693)

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - xen/arm: Boot modules are not scrubbed The bootloader will load boot modules (e.g. kernel, initramfs...)
    in a temporary area before they are copied by Xen to each domain memory. To ensure sensitive data is not
    leaked from the modules, Xen must "scrub" them before handing the page over to the allocator.
    Unfortunately, it was discovered that modules will not be scrubbed on Arm. (CVE-2021-28693)

The remote host is affected by the vulnerability described in GLSA-202107-30 (Xen: Multiple vulnerabilities)

    Multiple vulnerabilities have been discovered in Xen. Please review the       CVE identifiers referenced below for details.
  Impact :

    Please review the referenced CVE identifiers for details.
  Workaround :

    There is no known workaround at this time.

The remote SUSE Linux SUSE15 host has packages installed that are affected by multiple vulnerabilities as referenced in the openSUSE-SU-2021:1236-1 advisory.

  - Observable response discrepancy in some Intel(R) Processors may allow an authorized user to potentially     enable information disclosure via local access. (CVE-2021-0089)

  - x86: TSX Async Abort protections not restored after S3 This issue relates to the TSX Async Abort     speculative security vulnerability. Please see https://xenbits.xen.org/xsa/advisory-305.html for details.
    Mitigating TAA by disabling TSX (the default and preferred option) requires selecting a non-default     setting in MSR_TSX_CTRL. This setting isn't restored after S3 suspend. (CVE-2021-28690)

  - inappropriate x86 IOMMU timeout detection / handling IOMMUs process commands issued to them in parallel     with the operation of the CPU(s) issuing such commands. In the current implementation in Xen, asynchronous     notification of the completion of such commands is not used. Instead, the issuing CPU spin-waits for the     completion of the most recently issued command(s). Some of these waiting loops try to apply a timeout to     fail overly-slow commands. The course of action upon a perceived timeout actually being detected is     inappropriate: - on Intel hardware guests which did not originally cause the timeout may be marked as     crashed, - on AMD hardware higher layer callers would not be notified of the issue, making them continue     as if the IOMMU operation succeeded. (CVE-2021-28692)

  - xen/arm: Boot modules are not scrubbed The bootloader will load boot modules (e.g. kernel, initramfs...)     in a temporary area before they are copied by Xen to each domain memory. To ensure sensitive data is not     leaked from the modules, Xen must scrub them before handing the page over to the allocator.
    Unfortunately, it was discovered that modules will not be scrubbed on Arm. (CVE-2021-28693)

  - IOMMU page mapping issues on x86 T[his CNA information record relates to multiple CVEs; the text explains     which aspects/vulnerabilities correspond to which CVE.] Both AMD and Intel allow ACPI tables to specify     regions of memory which should be left untranslated, which typically means these addresses should pass the     translation phase unaltered. While these are typically device specific ACPI properties, they can also be     specified to apply to a range of devices, or even all devices. On all systems with such regions Xen failed     to prevent guests from undoing/replacing such mappings (CVE-2021-28694). On AMD systems, where a     discontinuous range is specified by firmware, the supposedly-excluded middle range will also be identity-     mapped (CVE-2021-28695). Further, on AMD systems, upon de-assigment of a physical device from a guest, the     identity mappings would be left in place, allowing a guest continued access to ranges of memory which it     shouldn't have access to anymore (CVE-2021-28696). (CVE-2021-28694, CVE-2021-28695, CVE-2021-28696)

  - grant table v2 status pages may remain accessible after de-allocation Guest get permitted access to     certain Xen-owned pages of memory. The majority of such pages remain allocated / associated with a guest     for its entire lifetime. Grant table v2 status pages, however, get de-allocated when a guest switched     (back) from v2 to v1. The freeing of such pages requires that the hypervisor know where in the guest these     pages were mapped. The hypervisor tracks only one use within guest space, but racing requests from the     guest to insert mappings of these pages may result in any of them to become mapped in multiple locations.
    Upon switching back from v2 to v1, the guest would then retain access to a page that was freed and perhaps     re-used for other purposes. (CVE-2021-28697)

  - long running loops in grant table handling In order to properly monitor resource use, Xen maintains     information on the grant mappings a domain may create to map grants offered by other domains. In the     process of carrying out certain actions, Xen would iterate over all such entries, including ones which     aren't in use anymore and some which may have been created but never used. If the number of entries for a     given domain is large enough, this iterating of the entire table may tie up a CPU for too long, starving     other domains or causing issues in the hypervisor itself. Note that a domain may map its own grants, i.e.
    there is no need for multiple domains to be involved here. A pair of cooperating guests may, however,     cause the effects to be more severe. (CVE-2021-28698)

  - inadequate grant-v2 status frames array bounds check The v2 grant table interface separates grant     attributes from grant status. That is, when operating in this mode, a guest has two tables. As a result,     guests also need to be able to retrieve the addresses that the new status tracking table can be accessed     through. For 32-bit guests on x86, translation of requests has to occur because the interface structure     layouts commonly differ between 32- and 64-bit. The translation of the request to obtain the frame numbers     of the grant status table involves translating the resulting array of frame numbers. Since the space used     to carry out the translation is limited, the translation layer tells the core function the capacity of the     array within translation space. Unfortunately the core function then only enforces array bounds to be     below 8 times the specified value, and would write past the available space if enough frame numbers needed     storing. (CVE-2021-28699)

  - xen/arm: No memory limit for dom0less domUs The dom0less feature allows an administrator to create     multiple unprivileged domains directly from Xen. Unfortunately, the memory limit from them is not set.
    This allow a domain to allocate memory beyond what an administrator originally configured.
    (CVE-2021-28700)

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

The remote SUSE Linux SLED12 / SLES12 / SLES_SAP12 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2021:2924-1 advisory.

    Security issues fixed:

    - CVE-2021-28693: xen/arm: Boot modules are not scrubbed (bsc#1186428)
    - CVE-2021-28692: xen: inappropriate x86 IOMMU timeout detection / handling (bsc#1186429)
    - CVE-2021-0089: xen: Speculative Code Store Bypass (bsc#1186433)
    - CVE-2021-28690: xen: x86: TSX Async Abort protections not restored after S3 (bsc#1186434)
    - CVE-2021-20255: Fixed stack overflow via infinite recursion in eepro100 (bsc#1182654)
    - CVE-2021-28694,CVE-2021-28695,CVE-2021-28696: IOMMU page mapping issues on x86 (XSA-378)(bsc#1189373).
    - CVE-2021-28697: grant table v2 status pages may remain accessible after de-allocation     (XSA-379)(bsc#1189376).
    - CVE-2021-28698: long running loops in grant table handling (XSA-380)(bsc#1189378).
    - CVE-2021-28699: inadequate grant-v2 status frames array bounds check (XSA-382)(bsc#1189380).
    - CVE-2021-28700: No memory limit for dom0less domUs (XSA-383)(bsc#1189381).
    - CVE-2021-3592: slirp: invalid pointer initialization may lead to information disclosure     (bootp)(bsc#1187369).
    - CVE-2021-3594: slirp: invalid pointer initialization may lead to information disclosure     (udp)(bsc#1187378).
    - CVE-2021-3595: slirp: invalid pointer initialization may lead to information disclosure     (tftp)(bsc#1187376).

    Other issues fixed:

    - Fixed 'Panic on CPU 0: IO-APIC + timer doesn't work!' (bsc#1180491)
    - Fixed an issue with xencommons, where file format expecations by fillup did not allign (bsc#1185682)
    - Upstream bug fixes (bsc#1027519)

    - Dom0 hangs when pinning CPUs for dom0 with HVM guest (bsc#1179246).
    - Fixed Xen SLES11SP4 guest hangs on cluster (bsc#1188050).
    - Fixed PVHVM SLES12 SP5 - NMI Watchdog CPU Stuck (bsc#1180846).
    - Core cannot be opened when using xl dump-core of VM with PTF (bsc#1183243)
    - Prevent superpage allocation in the LAPIC and ACPI_INFO range (bsc#1189882).

Tenable has extracted the preceding description block directly from the SUSE security advisory.

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

The remote SUSE Linux SLED15 / SLES15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2021:2922-1 advisory.

    Update to Xen 4.13.3 general bug fix release (bsc#1027519).

    Security issues fixed:

    - CVE-2021-28693: xen/arm: Boot modules are not scrubbed (bsc#1186428)
    - CVE-2021-28692: xen: inappropriate x86 IOMMU timeout detection / handling (bsc#1186429)
    - CVE-2021-0089: xen: Speculative Code Store Bypass (bsc#1186433)
    - CVE-2021-28690: xen: x86: TSX Async Abort protections not restored after S3 (bsc#1186434)
    - CVE-2021-28694,CVE-2021-28695,CVE-2021-28696: IOMMU page mapping issues on x86 (XSA-378)(bsc#1189373).
    - CVE-2021-28697: grant table v2 status pages may remain accessible after de-allocation     (XSA-379)(bsc#1189376).
    - CVE-2021-28698: long running loops in grant table handling (XSA-380)(bsc#1189378).
    - CVE-2021-28699: inadequate grant-v2 status frames array bounds check (XSA-382)(bsc#1189380).
    - CVE-2021-28700: No memory limit for dom0less domUs (XSA-383)(bsc#1189381).

    Other issues fixed:

    - Fixed 'Panic on CPU 0: IO-APIC + timer doesn't work!' (bsc#1180491)
    - Fixed an issue with xencommons, where file format expecations by fillup did not allign (bsc#1185682)
    - Fixed shell macro expansion in the spec file, so that ExecStart=       in xendomains-wait-disks.service is created correctly (bsc#1183877)
    - Upstream bug fixes (bsc#1027519)
    - Fixed Xen SLES11SP4 guest hangs on cluster (bsc#1188050).
    - xl monitoring process exits during xl save -p|-c keep the monitoring process running to cleanup the domU     during shutdown (bsc#1176189).
    - Dom0 hangs when pinning CPUs for dom0 with HVM guest (bsc#1179246).
    - Prevent superpage allocation in the LAPIC and ACPI_INFO range (bsc#1189882).

Tenable has extracted the preceding description block directly from the SUSE security advisory.

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

The remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2021:2925-1 advisory.

    Security issues fixed:

    - CVE-2021-28693: xen/arm: Boot modules are not scrubbed (bsc#1186428)
    - CVE-2021-28692: xen: inappropriate x86 IOMMU timeout detection / handling (bsc#1186429)
    - CVE-2021-0089: xen: Speculative Code Store Bypass (bsc#1186433)
    - CVE-2021-28690: xen: x86: TSX Async Abort protections not restored after S3 (bsc#1186434)

    - CVE-2021-28694,CVE-2021-28695,CVE-2021-28696: IOMMU page mapping issues on x86 (XSA-378)(bsc#1189373).
    - CVE-2021-28697: grant table v2 status pages may remain accessible after de-allocation     (XSA-379)(bsc#1189376).
    - CVE-2021-28698: long running loops in grant table handling (XSA-380)(bsc#1189378).
    - CVE-2021-28699: inadequate grant-v2 status frames array bounds check (XSA-382)(bsc#1189380).
    - CVE-2021-28700: No memory limit for dom0less domUs (XSA-383)(bsc#1189381).

    Other issues fixed:

    - Fixed 'Panic on CPU 0: IO-APIC + timer doesn't work!' (bsc#1180491)
    - Upstream bug fixes (bsc#1027519)
    - Dom0 hangs when pinning CPUs for dom0 with HVM guest (bsc#1179246).
    - Fixed Xen SLES11SP4 guest hangs on cluster (bsc#1188050).
    - Fixed PVHVM SLES12 SP5 - NMI Watchdog CPU Stuck (bsc#1180846).
    - Core cannot be opened when using xl dump-core of VM with PTF (bsc#1183243).
    - Prevent superpage allocation in the LAPIC and ACPI_INFO range (bsc#1189882).

Tenable has extracted the preceding description block directly from the SUSE security advisory.

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

The remote SUSE Linux SLED15 / SLES15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2021:2923-1 advisory.

    Update to Xen 4.13.3 general bug fix release (bsc#1027519).

    Security issues fixed:

    - CVE-2021-28693: xen/arm: Boot modules are not scrubbed (bsc#1186428)
    - CVE-2021-28692: xen: inappropriate x86 IOMMU timeout detection / handling (bsc#1186429)
    - CVE-2021-0089: xen: Speculative Code Store Bypass (bsc#1186433)
    - CVE-2021-28690: xen: x86: TSX Async Abort protections not restored after S3 (bsc#1186434)
    - CVE-2021-28694,CVE-2021-28695,CVE-2021-28696: IOMMU page mapping issues on x86 (XSA-378)(bsc#1189373).
    - CVE-2021-28697: grant table v2 status pages may remain accessible after de-allocation     (XSA-379)(bsc#1189376).
    - CVE-2021-28698: long running loops in grant table handling (XSA-380)(bsc#1189378).
    - CVE-2021-28699: inadequate grant-v2 status frames array bounds check (XSA-382)(bsc#1189380).
    - CVE-2021-28700: No memory limit for dom0less domUs (XSA-383)(bsc#1189381).

    Other issues fixed:

    - Fixed 'Panic on CPU 0: IO-APIC + timer doesn't work!' (bsc#1180491)
    - Fixed an issue with xencommons, where file format expecations by fillup did not allign (bsc#1185682)
    - Fixed shell macro expansion in the spec file, so that ExecStart=       in xendomains-wait-disks.service is created correctly (bsc#1183877)
    - Upstream bug fixes (bsc#1027519)
    - Fixed Xen SLES11SP4 guest hangs on cluster (bsc#1188050).
    - xl monitoring process exits during xl save -p|-c keep the monitoring process running to cleanup the domU     during shutdown (bsc#1176189).
    - Dom0 hangs when pinning CPUs for dom0 with HVM guest (bsc#1179246).
    - Some long deprecated commands were finally removed in qemu6. Adjust libxl to use supported commands     (bsc#1183243).
    - Update logrotate.conf, move global options into per-file sections to prevent globbering of global state     (bsc#1187406).
    - Prevent superpage allocation in the LAPIC and ACPI_INFO range (bsc#1189882).

Tenable has extracted the preceding description block directly from the SUSE security advisory.

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

The remote SUSE Linux SUSE15 host has packages installed that are affected by multiple vulnerabilities as referenced in the openSUSE-SU-2021:2923-1 advisory.

  - Observable response discrepancy in some Intel(R) Processors may allow an authorized user to potentially     enable information disclosure via local access. (CVE-2021-0089)

  - x86: TSX Async Abort protections not restored after S3 This issue relates to the TSX Async Abort     speculative security vulnerability. Please see https://xenbits.xen.org/xsa/advisory-305.html for details.
    Mitigating TAA by disabling TSX (the default and preferred option) requires selecting a non-default     setting in MSR_TSX_CTRL. This setting isn't restored after S3 suspend. (CVE-2021-28690)

  - inappropriate x86 IOMMU timeout detection / handling IOMMUs process commands issued to them in parallel     with the operation of the CPU(s) issuing such commands. In the current implementation in Xen, asynchronous     notification of the completion of such commands is not used. Instead, the issuing CPU spin-waits for the     completion of the most recently issued command(s). Some of these waiting loops try to apply a timeout to     fail overly-slow commands. The course of action upon a perceived timeout actually being detected is     inappropriate: - on Intel hardware guests which did not originally cause the timeout may be marked as     crashed, - on AMD hardware higher layer callers would not be notified of the issue, making them continue     as if the IOMMU operation succeeded. (CVE-2021-28692)

  - xen/arm: Boot modules are not scrubbed The bootloader will load boot modules (e.g. kernel, initramfs...)     in a temporary area before they are copied by Xen to each domain memory. To ensure sensitive data is not     leaked from the modules, Xen must scrub them before handing the page over to the allocator.
    Unfortunately, it was discovered that modules will not be scrubbed on Arm. (CVE-2021-28693)

  - IOMMU page mapping issues on x86 T[his CNA information record relates to multiple CVEs; the text explains     which aspects/vulnerabilities correspond to which CVE.] Both AMD and Intel allow ACPI tables to specify     regions of memory which should be left untranslated, which typically means these addresses should pass the     translation phase unaltered. While these are typically device specific ACPI properties, they can also be     specified to apply to a range of devices, or even all devices. On all systems with such regions Xen failed     to prevent guests from undoing/replacing such mappings (CVE-2021-28694). On AMD systems, where a     discontinuous range is specified by firmware, the supposedly-excluded middle range will also be identity-     mapped (CVE-2021-28695). Further, on AMD systems, upon de-assigment of a physical device from a guest, the     identity mappings would be left in place, allowing a guest continued access to ranges of memory which it     shouldn't have access to anymore (CVE-2021-28696). (CVE-2021-28694, CVE-2021-28695, CVE-2021-28696)

  - grant table v2 status pages may remain accessible after de-allocation Guest get permitted access to     certain Xen-owned pages of memory. The majority of such pages remain allocated / associated with a guest     for its entire lifetime. Grant table v2 status pages, however, get de-allocated when a guest switched     (back) from v2 to v1. The freeing of such pages requires that the hypervisor know where in the guest these     pages were mapped. The hypervisor tracks only one use within guest space, but racing requests from the     guest to insert mappings of these pages may result in any of them to become mapped in multiple locations.
    Upon switching back from v2 to v1, the guest would then retain access to a page that was freed and perhaps     re-used for other purposes. (CVE-2021-28697)

  - long running loops in grant table handling In order to properly monitor resource use, Xen maintains     information on the grant mappings a domain may create to map grants offered by other domains. In the     process of carrying out certain actions, Xen would iterate over all such entries, including ones which     aren't in use anymore and some which may have been created but never used. If the number of entries for a     given domain is large enough, this iterating of the entire table may tie up a CPU for too long, starving     other domains or causing issues in the hypervisor itself. Note that a domain may map its own grants, i.e.
    there is no need for multiple domains to be involved here. A pair of cooperating guests may, however,     cause the effects to be more severe. (CVE-2021-28698)

  - inadequate grant-v2 status frames array bounds check The v2 grant table interface separates grant     attributes from grant status. That is, when operating in this mode, a guest has two tables. As a result,     guests also need to be able to retrieve the addresses that the new status tracking table can be accessed     through. For 32-bit guests on x86, translation of requests has to occur because the interface structure     layouts commonly differ between 32- and 64-bit. The translation of the request to obtain the frame numbers     of the grant status table involves translating the resulting array of frame numbers. Since the space used     to carry out the translation is limited, the translation layer tells the core function the capacity of the     array within translation space. Unfortunately the core function then only enforces array bounds to be     below 8 times the specified value, and would write past the available space if enough frame numbers needed     storing. (CVE-2021-28699)

  - xen/arm: No memory limit for dom0less domUs The dom0less feature allows an administrator to create     multiple unprivileged domains directly from Xen. Unfortunately, the memory limit from them is not set.
    This allow a domain to allocate memory beyond what an administrator originally configured.
    (CVE-2021-28700)

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

According to its self-reported version number, the Xen hypervisor installed on the remote host is affected by an information disclosure vulnerability as boot modules are not scrubbed. The bootloader will load boot modules (e.g.
  kernel, initramfs...) in a temporary area before they are copied by Xen to each domain memory. To ensure sensitive data is not leaked from the modules, Xen must 'scrub' them before handing the page over to the allocator. Unfortunately, it was discovered that modules will not be scrubbed on Arm.

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

ID	Name	Product	Family	Severity
255327	Linux Distros Unpatched Vulnerability : CVE-2021-28693	Nessus	Misc.	medium
424702	Alpine: multiple xen packages: security update to 4.14.1-r3	Tenable Cloud Security	Alpine Linux Local Security Checks	high
424702	Alpine: multiple xen packages: security update to 4.14.1-r3	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	high
424664	Alpine: multiple xen packages: security update to 4.15.0-r1	Tenable Cloud Security	Alpine Linux Local Security Checks	high
424664	Alpine: multiple xen packages: security update to 4.15.0-r1	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	high
407781	Alpine: xen: security update to 4.13.3-r1	Tenable Cloud Security	Alpine Linux Local Security Checks	high
407781	Alpine: xen: security update to 4.13.3-r1	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	high
400204	Alpine: multiple xen packages: security update to 4.15.0-r0 (deprecated)	Tenable Cloud Security	Alpine Linux Local Security Checks	medium
400204	Alpine: multiple xen packages: security update to 4.15.0-r0 (deprecated)	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	medium
157004	GLSA-202107-30 : Xen: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	high
153108	openSUSE 15 Security Update : xen (openSUSE-SU-2021:1236-1)	Nessus	SuSE Local Security Checks	high
153017	SUSE SLED12: xen / xen-devel / xen-doc-html / xen-libs / xen-libs-32bit / etc (SUSE-SU-2021:2924-1)	Nessus	SuSE Local Security Checks	high
153016	SUSE SLED15: xen / xen-devel / xen-libs / xen-tools / xen-tools-domU / etc (SUSE-SU-2021:2922-1)	Nessus	SuSE Local Security Checks	high
153013	SUSE SLES15 Security Update : xen (SUSE-SU-2021:2925-1)	Nessus	SuSE Local Security Checks	high
153010	SUSE SLED15: xen / xen-devel / xen-libs / xen-tools / xen-tools-domU / etc (SUSE-SU-2021:2923-1)	Nessus	SuSE Local Security Checks	high
153009	openSUSE 15 Security Update : xen (openSUSE-SU-2021:2923-1)	Nessus	SuSE Local Security Checks	high
152209	Xen / ARM Boot Modules Are Not Scrubbed Information Exposure (XSA-372)	Nessus	Misc.	medium

Detections

Analytics

CVE-2021-28693

medium

Tenable Plugins

medium

high

high

high

high

high

high

medium

medium

high

high

high

high

high

high

high

medium