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 ALAS2NITRO-ENCLAVES-2024-048 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.

Detections

Analytics

Amazon Linux 2 : runc (ALASNITRO-ENCLAVES-2024-048)

low Nessus Plugin ID 209067

Version 1.2

Version 1.1

Version 1.2 Dec 12, 2024, 9:55 AM CVSS metrics ("Cvssv4 score" set to 0.0) CVSSv2 severity (based on None, severity decreased from "High" to "Low") Detection (updated detection logic) Plugin Feed: 202412120955
Version 1.1 Oct 16, 2024, 3:06 AM New Plugin Feed: 202410160306