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

    2024-08-28: CVE-2023-45289 was added to this 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)

    When following an HTTP redirect to a domain which is not a subdomain match or exact match of the initial     domain, an http.Client does not forward sensitive headers such as Authorization or Cookie. For     example, a redirect from foo.com to www.foo.com will forward the Authorization header, but a redirect to     bar.com will not. A maliciously crafted HTTP redirect could cause sensitive headers to be unexpectedly     forwarded. (CVE-2023-45289)

    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)

Tenable has extracted the preceding description block directly from the tested product 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 host is affected by the vulnerability described in GLSA-202409-29 (Docker: Multiple Vulnerabilities)

    Multiple vulnerabilities have been discovered in Docker. Please review the CVE identifiers referenced     below 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 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 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.

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 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-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 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:3120-1 advisory.

    Changes in docker:
    - CVE-2024-23651: Fixed arbitrary files write due to race condition on mounts (bsc#1219267)
    - CVE-2024-23652: Fixed insufficient validation of parent directory on mount (bsc#1219268)
    - CVE-2024-23653: Fixed insufficient validation on entitlement on container creation via buildkit     (bsc#1219438)
    - CVE-2024-41110: A Authz zero length regression that could lead to authentication bypass was fixed     (bsc#1228324)

    Other fixes:

    - Update to Docker 25.0.6-ce. See upstream changelog online at       <https://docs.docker.com/engine/release-notes/25.0/#2506>
    - Update to Docker 25.0.5-ce (bsc#1223409)

    - Fix BuildKit's symlink resolution logic to correctly handle non-lexical       symlinks. (bsc#1221916)
    - Write volume options atomically so sudden system crashes won't result in       future Docker starts failing due to empty files. (bsc#1214855)

    Changes in buildah:
    - Update to version 1.35.4:
      * [release-1.35] Bump to Buildah v1.35.4
      * [release-1.35] CVE-2024-3727 updates (bsc#1224117)
      * integration test: handle new labels in 'bud and test --unsetlabel'
      * [release-1.35] Bump go-jose CVE-2024-28180
      * [release-1.35] Bump ocicrypt and go-jose CVE-2024-28180

    - Update to version 1.35.3:
      * [release-1.35] Bump to Buildah v1.35.3
      * [release-1.35] correctly configure /etc/hosts and resolv.conf
      * [release-1.35] buildah: refactor resolv/hosts setup.
      * [release-1.35] rename the hostFile var to reflect
      * [release-1.35] Bump c/common to v0.58.1
      * [release-1.35] Bump Buildah to v1.35.2
      * [release-1.35] CVE-2024-24786 protobuf to 1.33
      * [release-1.35] Bump to v1.35.2-dev

    - Update to version 1.35.1:
      * [release-1.35] Bump to v1.35.1
      * [release-1.35] CVE-2024-1753 container escape fix (bsc#1221677)

    - Buildah dropped cni support, require netavark instead (bsc#1221243)

    - Remove obsolete requires libcontainers-image & libcontainers-storage

    - Require passt for rootless networking (poo#156955)       Buildah moved to passt/pasta for rootless networking from slirp4netns       (https://github.com/containers/common/pull/1846)

    - Update to version 1.35.0:
      * Bump v1.35.0
      * Bump c/common v0.58.0, c/image v5.30.0, c/storage v1.53.0
      * conformance tests: don't break on trailing zeroes in layer blobs
      * Add a conformance test for copying to a mounted prior stage
      * fix(deps): update module github.com/stretchr/testify to v1.9.0
      * cgroups: reuse version check from c/common
      * Update vendor of containers/(common,image)
      * fix(deps): update github.com/containers/storage digest to eadc620
      * fix(deps): update github.com/containers/luksy digest to ceb12d4
      * fix(deps): update github.com/containers/image/v5 digest to cdc6802
      * manifest add: complain if we get artifact flags without --artifact
      * Use retry logic from containers/common
      * Vendor in containers/(storage,image,common)
      * Update module golang.org/x/crypto to v0.20.0
      * Add comment re: Total Success task name
      * tests: skip_if_no_unshare(): check for --setuid
      * Properly handle build --pull=false
      * [skip-ci] Update tim-actions/get-pr-commits action to v1.3.1
      * Update module go.etcd.io/bbolt to v1.3.9
      * Revert 'Reduce official image size'
      * Update module github.com/opencontainers/image-spec to v1.1.0
      * Reduce official image size
      * Build with CNI support on FreeBSD
      * build --all-platforms: skip some base 'image' platforms
      * Bump main to v1.35.0-dev
      * Vendor in latest containers/(storage,image,common)
      * Split up error messages for missing --sbom related flags
      * `buildah manifest`: add artifact-related options
      * cmd/buildah/manifest.go: lock lists before adding/annotating/pushing
      * cmd/buildah/manifest.go: don't make struct declarations aliases
      * Use golang.org/x/exp/slices.Contains
      * Disable loong64 again
      * Fix a couple of typos in one-line comments
      * egrep is obsolescent; use grep -E
      * Try Cirrus with a newer VM version
      * Set CONTAINERS_CONF in the chroot-mount-flags integration test
      * Update to match dependency API update
      * Update github.com/openshift/imagebuilder and containers/common
      * docs: correct default authfile path
      * fix(deps): update module github.com/containerd/containerd to v1.7.13
      * tests: retrofit test for heredoc summary
      * build, heredoc: show heredoc summary in build output
      * manifest, push: add support for --retry and --retry-delay
      * fix(deps): update github.com/openshift/imagebuilder digest to b767bc3
      * imagebuildah: fix crash with empty RUN
      * fix(deps): update github.com/containers/luksy digest to b62d551
      * fix(deps): update module github.com/opencontainers/runc to v1.1.12 [security]
      * fix(deps): update module github.com/moby/buildkit to v0.12.5 [security]
      * Make buildah match podman for handling of ulimits
      * docs: move footnotes to where they're applicable
      * Allow users to specify no-dereference
      * Run codespell on code
      * Fix FreeBSD version parsing
      * Fix a build break on FreeBSD
      * Remove a bad FROM line
      * fix(deps): update module github.com/onsi/gomega to v1.31.1
      * fix(deps): update module github.com/opencontainers/image-spec to v1.1.0-rc6
      * docs: use reversed logo for dark theme in README
      * build,commit: add --sbom to scan and produce SBOMs when committing
      * commit: force omitHistory if the parent has layers but no history
      * docs: fix a couple of typos
      * internal/mkcw.Archive(): handle extra image content
      * stage_executor,heredoc: honor interpreter in heredoc
      * stage_executor,layers: burst cache if heredoc content is changed
      * fix(deps): update module golang.org/x/crypto to v0.18.0
      * Replace map[K]bool with map[K]struct{} where it makes sense
      * fix(deps): update module golang.org/x/sync to v0.6.0
      * fix(deps): update module golang.org/x/term to v0.16.0
      * Bump CI VMs
      * Replace strings.SplitN with strings.Cut
      * fix(deps): update github.com/containers/storage digest to ef81e9b
      * fix(deps): update github.com/containers/image/v5 digest to 1b221d4
      * fix(deps): update module github.com/fsouza/go-dockerclient to v1.10.1
      * Document use of containers-transports values in buildah
      * fix(deps): update module golang.org/x/crypto to v0.17.0 [security]
      * chore(deps): update dependency containers/automation_images to v20231208
      * manifest: addCompression use default from containers.conf
      * commit: add a --add-file flag
      * mkcw: populate the rootfs using an overlay
      * chore(deps): update dependency containers/automation_images to v20230517
      * [skip-ci] Update actions/stale action to v9
      * fix(deps): update module github.com/containernetworking/plugins to v1.4.0
      * fix(deps): update github.com/containers/image/v5 digest to 7a40fee
      * Bump to v1.34.1-dev
      * Ignore errors if label.Relabel returns ENOSUP

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 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 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 / 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.

ID	Name	Product	Family	Published	Updated	Severity
191617	Amazon Linux 2023 : docker (ALAS2023-2024-542)	Nessus	Amazon Linux Local Security Checks	3/6/2024	8/29/2024	critical
207893	GLSA-202409-29 : Docker: Multiple Vulnerabilities	Nessus	Gentoo Local Security Checks	9/28/2024	9/28/2024	critical
190364	Docker Desktop < 4.27.1 Multiple Vulnerabilities	Nessus	MacOS X Local Security Checks	2/9/2024	9/23/2024	critical
190363	Docker Desktop < 4.27.1 Multiple Vulnerabilities	Nessus	Windows	2/9/2024	9/23/2024	critical
201915	GLSA-202407-12 : podman: Multiple Vulnerabilities	Nessus	Gentoo Local Security Checks	7/5/2024	7/5/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
202108	GLSA-202407-25 : Buildah: Multiple Vulnerabilities	Nessus	Gentoo Local Security Checks	7/10/2024	7/10/2024	critical
206581	SUSE SLES15 / openSUSE 15 Security Update : buildah, docker (SUSE-SU-2024:3120-1)	Nessus	SuSE Local Security Checks	9/4/2024	9/4/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
190365	Docker Desktop < 4.27.1 Multiple Vulnerabilities	Nessus	Misc.	2/9/2024	9/23/2024	critical
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

Detections

Analytics

Plugins Search

critical

critical

critical

critical

critical

critical

critical

critical

high

critical

critical

critical

critical