It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2024-542 advisory.

  - A malicious HTTP sender can use chunk extensions to cause a receiver reading from a request or response     body to read many more bytes from the network than are in the body. A malicious HTTP client can further     exploit this to cause a server to automatically read a large amount of data (up to about 1GiB) when a     handler fails to read the entire body of a request. Chunk extensions are a little-used HTTP feature which     permit including additional metadata in a request or response body sent using the chunked encoding. The     net/http chunked encoding reader discards this metadata. A sender can exploit this by inserting a large     metadata segment with each byte transferred. The chunk reader now produces an error if the ratio of real     body to encoded bytes grows too small. (CVE-2023-39326)

  - BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and     repeatable manner. A malicious BuildKit client or frontend could craft a request that could lead to     BuildKit daemon crashing with a panic. The issue has been fixed in v0.12.5. As a workaround, avoid using     BuildKit frontends from untrusted sources. (CVE-2024-23650)

  - BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and     repeatable manner. Two malicious build steps running in parallel sharing the same cache mounts with     subpaths could cause a race condition that can lead to files from the host system being accessible to the     build container. The issue has been fixed in v0.12.5. Workarounds include, avoiding using BuildKit     frontend from an untrusted source or building an untrusted Dockerfile containing cache mounts with
    --mount=type=cache,source=... options. (CVE-2024-23651)

  - BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and     repeatable manner. A malicious BuildKit frontend or Dockerfile using RUN --mount could trick the feature     that removes empty files created for the mountpoints into removing a file outside the container, from the     host system. The issue has been fixed in v0.12.5. Workarounds include avoiding using BuildKit frontends     from an untrusted source or building an untrusted Dockerfile containing RUN --mount feature.
    (CVE-2024-23652)

  - BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and     repeatable manner. In addition to running containers as build steps, BuildKit also provides APIs for     running interactive containers based on built images. It was possible to use these APIs to ask BuildKit to     run a container with elevated privileges. Normally, running such containers is only allowed if special     `security.insecure` entitlement is enabled both by buildkitd configuration and allowed by the user     initializing the build request. The issue has been fixed in v0.12.5 . Avoid using BuildKit frontends from     untrusted sources. (CVE-2024-23653)

  - Moby is an open-source project created by Docker to enable software containerization. The classic builder     cache system is prone to cache poisoning if the image is built FROM scratch. Also, changes to some     instructions (most important being HEALTHCHECK and ONBUILD) would not cause a cache miss. An attacker with     the knowledge of the Dockerfile someone is using could poison their cache by making them pull a specially     crafted image that would be considered as a valid cache candidate for some build steps. 23.0+ users are     only affected if they explicitly opted out of Buildkit (DOCKER_BUILDKIT=0 environment variable) or are     using the /build API endpoint. All users on versions older than 23.0 could be impacted. Image build API     endpoint (/build) and ImageBuild function from github.com/docker/docker/client is also affected as it the     uses classic builder by default. Patches are included in 24.0.9 and 25.0.2 releases. (CVE-2024-24557)

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

The version of Docker Desktop for Mac is prior to 4.27.1. It is therefore affected by multiple vulnerabilities.

  - runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. In     runc 1.1.11 and earlier, due to an internal file descriptor leak, an attacker could cause a newly-spawned     container process (from runc exec) to have a working directory in the host filesystem namespace, allowing     for a container escape by giving access to the host filesystem (attack 2). The same attack could be used     by a malicious image to allow a container process to gain access to the host filesystem through runc run     (attack 1). Variants of attacks 1 and 2 could be also be used to overwrite semi-arbitrary host binaries,     allowing for complete container escapes (attack 3a and attack 3b). runc 1.1.12 includes patches for this     issue. (CVE-2024-21626)

  - BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and     repeatable manner. A malicious BuildKit client or frontend could craft a request that could lead to     BuildKit daemon crashing with a panic. The issue has been fixed in v0.12.5. As a workaround, avoid using     BuildKit frontends from untrusted sources. (CVE-2024-23650)

  - BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and     repeatable manner. Two malicious build steps running in parallel sharing the same cache mounts with     subpaths could cause a race condition that can lead to files from the host system being accessible to     the build container. The issue has been fixed in v0.12.5. Workarounds include, avoiding using BuildKit     frontend from an untrusted source or building an untrusted Dockerfile containing cache mounts with 
    --mount=type=cache,source=... options. (CVE-2024-23651)

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

The remote host is affected by the vulnerability described in GLSA-202407-25 (Buildah: Multiple Vulnerabilities)

    Please review the referenced CVE identifiers for details.

Tenable has extracted the preceding description block directly from the Gentoo Linux 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 version of moby-engine 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-23651 advisory.

  - BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and     repeatable manner. Two malicious build steps running in parallel sharing the same cache mounts with     subpaths could cause a race condition that can lead to files from the host system being accessible to the     build container. The issue has been fixed in v0.12.5. Workarounds include, avoiding using BuildKit     frontend from an untrusted source or building an untrusted Dockerfile containing cache mounts with
    --mount=type=cache,source=... options. (CVE-2024-23651)

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

  - BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and     repeatable manner. Two malicious build steps running in parallel sharing the same cache mounts with     subpaths could cause a race condition that can lead to files from the host system being accessible to the     build container. The issue has been fixed in v0.12.5. Workarounds include, avoiding using BuildKit     frontend from an untrusted source or building an untrusted Dockerfile containing cache mounts with
    --mount=type=cache,source=... options. (CVE-2024-23651)

  - BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and     repeatable manner. A malicious BuildKit frontend or Dockerfile using RUN --mount could trick the feature     that removes empty files created for the mountpoints into removing a file outside the container, from the     host system. The issue has been fixed in v0.12.5. Workarounds include avoiding using BuildKit frontends     from an untrusted source or building an untrusted Dockerfile containing RUN --mount feature.
    (CVE-2024-23652)

  - BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and     repeatable manner. In addition to running containers as build steps, BuildKit also provides APIs for     running interactive containers based on built images. It was possible to use these APIs to ask BuildKit to     run a container with elevated privileges. Normally, running such containers is only allowed if special     `security.insecure` entitlement is enabled both by buildkitd configuration and allowed by the user     initializing the build request. The issue has been fixed in v0.12.5 . Avoid using BuildKit frontends from     untrusted sources. (CVE-2024-23653)

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 multiple vulnerabilities as referenced in the SUSE-SU-2024:0587-1 advisory.

  - BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and     repeatable manner. Two malicious build steps running in parallel sharing the same cache mounts with     subpaths could cause a race condition that can lead to files from the host system being accessible to the     build container. The issue has been fixed in v0.12.5. Workarounds include, avoiding using BuildKit     frontend from an untrusted source or building an untrusted Dockerfile containing cache mounts with
    --mount=type=cache,source=... options. (CVE-2024-23651)

  - BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and     repeatable manner. A malicious BuildKit frontend or Dockerfile using RUN --mount could trick the feature     that removes empty files created for the mountpoints into removing a file outside the container, from the     host system. The issue has been fixed in v0.12.5. Workarounds include avoiding using BuildKit frontends     from an untrusted source or building an untrusted Dockerfile containing RUN --mount feature.
    (CVE-2024-23652)

  - BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and     repeatable manner. In addition to running containers as build steps, BuildKit also provides APIs for     running interactive containers based on built images. It was possible to use these APIs to ask BuildKit to     run a container with elevated privileges. Normally, running such containers is only allowed if special     `security.insecure` entitlement is enabled both by buildkitd configuration and allowed by the user     initializing the build request. The issue has been fixed in v0.12.5 . Avoid using BuildKit frontends from     untrusted sources. (CVE-2024-23653)

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 multiple vulnerabilities as referenced in the SUSE-SU-2024:1469-1 advisory.

  - BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and     repeatable manner. Two malicious build steps running in parallel sharing the same cache mounts with     subpaths could cause a race condition that can lead to files from the host system being accessible to the     build container. The issue has been fixed in v0.12.5. Workarounds include, avoiding using BuildKit     frontend from an untrusted source or building an untrusted Dockerfile containing cache mounts with
    --mount=type=cache,source=... options. (CVE-2024-23651)

  - BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and     repeatable manner. A malicious BuildKit frontend or Dockerfile using RUN --mount could trick the feature     that removes empty files created for the mountpoints into removing a file outside the container, from the     host system. The issue has been fixed in v0.12.5. Workarounds include avoiding using BuildKit frontends     from an untrusted source or building an untrusted Dockerfile containing RUN --mount feature.
    (CVE-2024-23652)

  - BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and     repeatable manner. In addition to running containers as build steps, BuildKit also provides APIs for     running interactive containers based on built images. It was possible to use these APIs to ask BuildKit to     run a container with elevated privileges. Normally, running such containers is only allowed if special     `security.insecure` entitlement is enabled both by buildkitd configuration and allowed by the user     initializing the build request. The issue has been fixed in v0.12.5 . Avoid using BuildKit frontends from     untrusted sources. (CVE-2024-23653)

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

The version of Docker Desktop for Linux is prior to 4.27.1. It is therefore affected by multiple vulnerabilities.

  - runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. In     runc 1.1.11 and earlier, due to an internal file descriptor leak, an attacker could cause a newly-spawned     container process (from runc exec) to have a working directory in the host filesystem namespace, allowing     for a container escape by giving access to the host filesystem (attack 2). The same attack could be used     by a malicious image to allow a container process to gain access to the host filesystem through runc run     (attack 1). Variants of attacks 1 and 2 could be also be used to overwrite semi-arbitrary host binaries,     allowing for complete container escapes (attack 3a and attack 3b). runc 1.1.12 includes patches for this     issue. (CVE-2024-21626)

  - BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and     repeatable manner. A malicious BuildKit client or frontend could craft a request that could lead to     BuildKit daemon crashing with a panic. The issue has been fixed in v0.12.5. As a workaround, avoid using     BuildKit frontends from untrusted sources. (CVE-2024-23650)

  - BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and     repeatable manner. Two malicious build steps running in parallel sharing the same cache mounts with     subpaths could cause a race condition that can lead to files from the host system being accessible to     the build container. The issue has been fixed in v0.12.5. Workarounds include, avoiding using BuildKit     frontend from an untrusted source or building an untrusted Dockerfile containing cache mounts with 
    --mount=type=cache,source=... options. (CVE-2024-23651)

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-2024:0586-2 advisory.

  - BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and     repeatable manner. Two malicious build steps running in parallel sharing the same cache mounts with     subpaths could cause a race condition that can lead to files from the host system being accessible to the     build container. The issue has been fixed in v0.12.5. Workarounds include, avoiding using BuildKit     frontend from an untrusted source or building an untrusted Dockerfile containing cache mounts with
    --mount=type=cache,source=... options. (CVE-2024-23651)

  - BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and     repeatable manner. A malicious BuildKit frontend or Dockerfile using RUN --mount could trick the feature     that removes empty files created for the mountpoints into removing a file outside the container, from the     host system. The issue has been fixed in v0.12.5. Workarounds include avoiding using BuildKit frontends     from an untrusted source or building an untrusted Dockerfile containing RUN --mount feature.
    (CVE-2024-23652)

  - BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and     repeatable manner. In addition to running containers as build steps, BuildKit also provides APIs for     running interactive containers based on built images. It was possible to use these APIs to ask BuildKit to     run a container with elevated privileges. Normally, running such containers is only allowed if special     `security.insecure` entitlement is enabled both by buildkitd configuration and allowed by the user     initializing the build request. The issue has been fixed in v0.12.5 . Avoid using BuildKit frontends from     untrusted sources. (CVE-2024-23653)

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

The remote host is affected by the vulnerability described in GLSA-202407-12 (podman: Multiple Vulnerabilities)

    Please review the referenced CVE identifiers for details.

Tenable has extracted the preceding description block directly from the Gentoo Linux 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 version of Docker Desktop for Windows is prior to 4.27.1. It is therefore affected by multiple vulnerabilities.

  - runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. In     runc 1.1.11 and earlier, due to an internal file descriptor leak, an attacker could cause a newly-spawned     container process (from runc exec) to have a working directory in the host filesystem namespace, allowing     for a container escape by giving access to the host filesystem (attack 2). The same attack could be used     by a malicious image to allow a container process to gain access to the host filesystem through runc run     (attack 1). Variants of attacks 1 and 2 could be also be used to overwrite semi-arbitrary host binaries,     allowing for complete container escapes (attack 3a and attack 3b). runc 1.1.12 includes patches for this     issue. (CVE-2024-21626)

  - BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and     repeatable manner. A malicious BuildKit client or frontend could craft a request that could lead to     BuildKit daemon crashing with a panic. The issue has been fixed in v0.12.5. As a workaround, avoid using     BuildKit frontends from untrusted sources. (CVE-2024-23650)

  - BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and     repeatable manner. Two malicious build steps running in parallel sharing the same cache mounts with     subpaths could cause a race condition that can lead to files from the host system being accessible to     the build container. The issue has been fixed in v0.12.5. Workarounds include, avoiding using BuildKit     frontend from an untrusted source or building an untrusted Dockerfile containing cache mounts with 
    --mount=type=cache,source=... options. (CVE-2024-23651)

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	Published	Updated	Severity
191617	Amazon Linux 2023 : docker (ALAS2023-2024-542)	Nessus	Amazon Linux Local Security Checks	3/6/2024	3/8/2024	critical
190364	Docker Desktop < 4.27.1 Multiple Vulnerabilities	Nessus	MacOS X Local Security Checks	2/9/2024	2/12/2024	critical
202108	GLSA-202407-25 : Buildah: Multiple Vulnerabilities	Nessus	Gentoo Local Security Checks	7/10/2024	7/10/2024	critical
191679	CBL Mariner 2.0 Security Update: moby-engine (CVE-2024-23651)	Nessus	MarinerOS Local Security Checks	3/7/2024	3/7/2024	high
190918	SUSE SLES15 / openSUSE 15 Security Update : docker (SUSE-SU-2024:0586-1)	Nessus	SuSE Local Security Checks	2/23/2024	2/23/2024	critical
190925	SUSE SLES12 Security Update : docker (SUSE-SU-2024:0587-1)	Nessus	SuSE Local Security Checks	2/23/2024	2/23/2024	critical
194741	SUSE SLES12 Security Update : docker (SUSE-SU-2024:1469-1)	Nessus	SuSE Local Security Checks	4/30/2024	4/30/2024	critical
190365	Docker Desktop < 4.27.1 Multiple Vulnerabilities	Nessus	Misc.	2/9/2024	4/26/2024	critical
192984	SUSE SLES15 Security Update : docker (SUSE-SU-2024:0586-2)	Nessus	SuSE Local Security Checks	4/8/2024	4/8/2024	critical
201915	GLSA-202407-12 : podman: Multiple Vulnerabilities	Nessus	Gentoo Local Security Checks	7/5/2024	7/5/2024	critical
190363	Docker Desktop < 4.27.1 Multiple Vulnerabilities	Nessus	Windows	2/9/2024	2/12/2024	critical

Detections

Analytics

Plugins Search

critical

critical

critical

high

critical

critical

critical

critical

critical

critical

critical