According to the versions of the docker-runc package installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

    runc is a CLI tool for spawning and running containers according to the OCI specification.runc 1.1.13 and     earlier, as well as 1.2.0-rc2 and earlier, can be tricked into creating empty files or directories in     arbitrary locations in the host filesystem by sharing a volume between two containers and exploiting a     race with `os.MkdirAll`.While this could be used to create empty files, existing files would not be     truncated.An attacker must have the ability to start containers using some kind of custom volume     configuration.Containers using user namespaces are still affected, but the scope of places an attacker can     create inodes can be significantly reduced.Sufficiently strict LSM policies (SELinux/Apparmor) can also in     principle block this attack -- we suspect the industry standard SELinux policy may restrict this attack's     scope but the exact scope of protection hasn't been analysed.This is exploitable using runc directly as     well as through Docker and Kubernetes.The issue is fixed in runc v1.1.14 and v1.2.0-rc3. Some workarounds     are available.Using user namespaces restricts this attack fairly significantly such that the attacker can     only create inodes in directories that the remapped root user/group has write access to.Unless the root     user is remapped to an actual user on the host (such as with rootless containers that don't use     `/etc/sub[ug]id`), this in practice means that an attacker would only be able to create inodes in world-     writable directories.A strict enough SELinux or AppArmor policy could in principle also restrict the scope     if a specific label is applied to the runc runtime, though neither the extent to which the standard     existing policies block this attack nor what exact policies are needed to sufficiently restrict this     attack have been thoroughly tested.(CVE-2024-45310)

Tenable has extracted the preceding description block directly from the EulerOS docker-runc security advisory.

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

According to the versions of the docker-runc package installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

    runc is a CLI tool for spawning and running containers according to the OCI specification. runc 1.1.13 and     earlier, as well as 1.2.0-rc2 and earlier, can be tricked into creating empty files or directories in     arbitrary locations in the host filesystem by sharing a volume between two containers and exploiting a     race with `os.MkdirAll`. While this could be used to create empty files, existing files would not be     truncated. An attacker must have the ability to start containers using some kind of custom volume     configuration. Containers using user namespaces are still affected, but the scope of places an attacker     can create inodes can be significantly reduced. Sufficiently strict LSM policies (SELinux/Apparmor) can     also in principle block this attack -- we suspect the industry standard SELinux policy may restrict this     attack's scope but the exact scope of protection hasn't been analysed. This is exploitable using runc     directly as well as through Docker and Kubernetes. The issue is fixed in runc v1.1.14 and v1.2.0-rc3.Some     workarounds are available. Using user namespaces restricts this attack fairly significantly such that the     attacker can only create inodes in directories that the remapped root user/group has write access to.
    Unless the root user is remapped to an actual user on the host (such as with rootless containers that     don't use `/etc/sub[ug]id`), this in practice means that an attacker would only be able to create inodes     in world-writable directories. A strict enough SELinux or AppArmor policy could in principle also restrict     the scope if a specific label is applied to the runc runtime, though neither the extent to which the     standard existing policies block this attack nor what exact policies are needed to sufficiently restrict     this attack have been thoroughly tested.(CVE-2024-45310)

Tenable has extracted the preceding description block directly from the EulerOS docker-runc security advisory.

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 SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:0479-1 advisory.

    Update to version 1.7.0. (bsc#1257128)

      Release notes https://github.com/kubevirt/kubevirt/releases/tag/v1.7.0

    - CVE-2025-64435: Fixes logic flaw in the virt-controller can lead to incorrect status updates and     potentially causing a DoS (bsc#1253189 )
    - CVE-2024-45310: Fixes kubevirt vendored github.com/opencontainers/runc/libcontainer/utils: runc can be     tricked into creating empty files/directories on host bsc#1257422

    - Upstream now uses stateless firmware for CoCo VMs.

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 SLES12 / SLES_SAP12 host has a package installed that is affected by a vulnerability as referenced in the SUSE-SU-2024:3324-1 advisory.

    - Update to runc v1.1.14
    - CVE-2024-45310: Fixed an issue where runc can be tricked into creating empty files/directories on host.
    (bsc#1230092)

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

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

The version of runc installed on the remote host is prior to 1.1.14-1. It is, therefore, affected by a vulnerability as referenced in the ALAS2DOCKER-2024-047 advisory.

    runc is a CLI tool for spawning and running containers according to the OCI specification. runc 1.1.13 and     earlier, as well as 1.2.0-rc2 and earlier, can be tricked into creating empty files or directories in     arbitrary locations in the host filesystem by sharing a volume between two containers and exploiting a     race with `os.MkdirAll`. While this could be used to create empty files, existing files would not be     truncated. An attacker must have the ability to start containers using some kind of custom volume     configuration. Containers using user namespaces are still affected, but the scope of places an attacker     can create inodes can be significantly reduced. Sufficiently strict LSM policies (SELinux/Apparmor) can     also in principle block this attack -- we suspect the industry standard SELinux policy may restrict this     attack's scope but the exact scope of protection hasn't been analysed. This is exploitable using runc     directly as well as through Docker and Kubernetes. The issue is fixed in runc v1.1.14 and v1.2.0-rc3.

    Some workarounds are available. Using user namespaces restricts this attack fairly significantly such that     the attacker can only create inodes in directories that the remapped root user/group has write access to.
    Unless the root user is remapped to an actualuser on the host (such as with rootless containers that don't     use `/etc/sub[ug]id`), this in practice means that an attacker would only be able to create inodes in     world-writable directories. A strict enough SELinux or AppArmor policy could in principle also restrict     the scope if a specific label is applied to the runc runtime, though neither the extent to which the     standard existing policies block this attack nor what exact policies are needed to sufficiently restrict     this attack have been thoroughly tested. (CVE-2024-45310)

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

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

The version of ecs-init installed on the remote host is prior to 1.89.1-1. It is, therefore, affected by a vulnerability as referenced in the ALAS2ECS-2025-050 advisory.

    runc is a CLI tool for spawning and running containers according to the OCI specification. runc 1.1.13 and     earlier, as well as 1.2.0-rc2 and earlier, can be tricked into creating empty files or directories in     arbitrary locations in the host filesystem by sharing a volume between two containers and exploiting a     race with `os.MkdirAll`. While this could be used to create empty files, existing files would not be     truncated. An attacker must have the ability to start containers using some kind of custom volume     configuration. Containers using user namespaces are still affected, but the scope of places an attacker     can create inodes can be significantly reduced. Sufficiently strict LSM policies (SELinux/Apparmor) can     also in principle block this attack -- we suspect the industry standard SELinux policy may restrict this     attack's scope but the exact scope of protection hasn't been analysed. This is exploitable using runc     directly as well as through Docker and Kubernetes. The issue is fixed in runc v1.1.14 and v1.2.0-rc3.

    Some workarounds are available. Using user namespaces restricts this attack fairly significantly such that     the attacker can only create inodes in directories that the remapped root user/group has write access to.
    Unless the root user is remapped to an actualuser on the host (such as with rootless containers that don't     use `/etc/sub[ug]id`), this in practice means that an attacker would only be able to create inodes in     world-writable directories. A strict enough SELinux or AppArmor policy could in principle also restrict     the scope if a specific label is applied to the runc runtime, though neither the extent to which the     standard existing policies block this attack nor what exact policies are needed to sufficiently restrict     this attack have been thoroughly tested. (CVE-2024-45310)

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

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

The version of cri-tools / moby-runc / runc installed on the remote CBL Mariner 2.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2024-45310 advisory.

  - runc is a CLI tool for spawning and running containers according to the OCI specification. runc 1.1.13 and     earlier, as well as 1.2.0-rc2 and earlier, can be tricked into creating empty files or directories in     arbitrary locations in the host filesystem by sharing a volume between two containers and exploiting a     race with `os.MkdirAll`. While this could be used to create empty files, existing files would not be     truncated. An attacker must have the ability to start containers using some kind of custom volume     configuration. Containers using user namespaces are still affected, but the scope of places an attacker     can create inodes can be significantly reduced. Sufficiently strict LSM policies (SELinux/Apparmor) can     also in principle block this attack -- we suspect the industry standard SELinux policy May restrict this     attack's scope but the exact scope of protection hasn't been analysed. This is exploitable using runc     directly as well as through Docker and Kubernetes. The issue is fixed in runc v1.1.14 and v1.2.0-rc3. Some     workarounds are available. Using user namespaces restricts this attack fairly significantly such that the     attacker can only create inodes in directories that the remapped root user/group has write access to.
    Unless the root user is remapped to an actual user on the host (such as with rootless containers that     don't use `/etc/sub[ug]id`), this in practice means that an attacker would only be able to create inodes     in world-writable directories. A strict enough SELinux or AppArmor policy could in principle also restrict     the scope if a specific label is applied to the runc runtime, though neither the extent to which the     standard existing policies block this attack nor what exact policies are needed to sufficiently restrict     this attack have been thoroughly tested. (CVE-2024-45310)

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 SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 host has a package installed that is affected by a vulnerability as referenced in the SUSE-SU-2025:02198-2 advisory.

    - CVE-2024-45310: Fixed unintentional creation of empty files/directories on host (bsc#1230092)

    Other fixes:

    - Update to runc v1.2.6.

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

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 SLES15 / openSUSE 15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:0439-1 advisory.

    Security fixes:

    - CVE-2024-45310: Fixed runc being tricked into creating empty       files/directories on host (bsc#1257432)
    - CVE-2025-65105: Fixed security bypass due to disabling security       options (bsc#1255462)
    - CVE-2025-47914: Fixed malformed constraint may cause denial of       service in golang.org/x/crypto/ssh/agent (bsc#1253967)
    - CVE-2025-58181: Fixed unbounded memory consumption in       golang.org/x/crypto/ssh (bsc#1253784)
    - CVE-2025-47913: Fixed potential denial of service in       golang.org/x/crypto/ssh/agent (bsc#1253506)
    - CVE-2025-22872: Fixed incorrect Neutralization of Input During       Web Page Generation in x/net (bsc#1241710)
    - CVE-2025-22870: Fixed HTTP Proxy bypass using IPv6 Zone IDs in       golang.org/x/net (bsc#1238611)
    - CVE-2025-22869: Fixed potential denial of service in       golang.org/x/crypto (bsc#1239322)
    - CVE-2025-27144: Fixed DoS in go-jose Parsing in       github.com/go-jose/go-jose (bsc#1237608)
    - CVE-2025-8556: Fixed missing and wrong validation can lead       to incorrect results in github.com/cloudflare/circl

    Other fixes:

    - Update to 1.4.5

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.

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
210688	EulerOS 2.0 SP10 : docker-runc (EulerOS-SA-2024-2883)	Nessus	Huawei Local Security Checks	2024/11/8	2024/11/8	low
212606	EulerOS 2.0 SP11 : docker-runc (EulerOS-SA-2024-2979)	Nessus	Huawei Local Security Checks	2024/12/12	2024/12/12	low
298915	SUSE SLES15 Security Update : kubevirt, virt-api-container, virt-controller-container, virt-exportproxy-container, virt-exportserver-container, virt-handler-container, virt-launcher-container, virt-libguestfs-tools-container, virt-operator-container, virt-pr-helper-container, virt-synchronization-controller-container (SUSE-SU-2026:0479-1)	Nessus	SuSE Local Security Checks	2026/2/13	2026/2/13	medium
207508	SUSE SLES12 Security Update : runc (SUSE-SU-2024:3324-1)	Nessus	SuSE Local Security Checks	2024/9/20	2024/9/20	low
209065	Amazon Linux 2 : runc (ALASDOCKER-2024-047)	Nessus	Amazon Linux Local Security Checks	2024/10/15	2024/12/11	low
212653	EulerOS 2.0 SP11 : docker-runc (EulerOS-SA-2024-2965)	Nessus	Huawei Local Security Checks	2024/12/12	2024/12/12	low
232221	Amazon Linux 2 : ecs-init (ALASECS-2025-050)	Nessus	Amazon Linux Local Security Checks	2025/3/6	2025/3/6	low
233946	CBL Mariner 2.0 Security Update: cri-tools / moby-runc / runc (CVE-2024-45310)	Nessus	MarinerOS Local Security Checks	2025/4/6	2026/1/22	medium
242222	SUSE SLED15 / SLES15 Security Update : runc (SUSE-SU-2025:02198-2)	Nessus	SuSE Local Security Checks	2025/7/17	2025/7/17	medium
298751	SUSE SLES15 / openSUSE 15 Security Update : apptainer (SUSE-SU-2026:0439-1)	Nessus	SuSE Local Security Checks	2026/2/12	2026/2/12	high

检测

插件搜索

low

low

medium

low

low

low

low

medium

medium

high