cve.bz

CVE-2024-29018 mobyproject moby

7.5 highEPSS 0.8%Fix available

High (7.5) in mobyproject moby. EPSS 0.8% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/docker/docker 23.0.11, 25.0.5, 25.0.5+incompatible.

On this page
Moby is an open source container framework that is a key component of Docker Engine, Docker Desktop, and other distributions of container tooling or runtimes. Moby's networking implementation allows for many networks, each with their own IP address range and gateway, to be defined. This feature is frequently referred to as custom networks, as each network can have a different driver, set of parameters and thus behaviors. When creating a network, the `--internal` flag is used to designate a network as _internal_. The `internal` attribute in a docker-compose.yml file may also be used to mark a network _internal_, and other API clients may specify the `internal` parameter as well. When containers with networking are created, they are assigned unique network interfaces and IP addresses. The host serves as a router for non-internal networks, with a gateway IP that provides SNAT/DNAT to/from container IPs. Containers on an internal network may communicate between each other, but are precluded from communicating with any networks the host has access to (LAN or WAN) as no default route is configured, and firewall rules are set up to drop all outgoing traffic. Communication with the gateway IP address (and thus appropriately configured host services) is possible, and the host may communicate with any container IP directly. In addition to configuring the Linux kernel's various networking features to enable container networking, `dockerd` directly provides some services to container networks. Principal among these is serving as a resolver, enabling service discovery, and resolution of names from an upstream resolver. When a DNS request for a name that does not correspond to a container is received, the request is forwarded to the configured upstream resolver. This request is made from the container's network namespace: the level of access and routing of traffic is the same as if the request was made by the container itself. As a consequence of this design, containers solely attached to an internal network will be unable to resolve names using the upstream resolver, as the container itself is unable to communicate with that nameserver. Only the names of containers also attached to the internal network are able to be resolved. Many systems run a local forwarding DNS resolver. As the host and any containers have separate loopback devices, a consequence of the design described above is that containers are unable to resolve names from the host's configured resolver, as they cannot reach these addresses on the host loopback device. To bridge this gap, and to allow containers to properly resolve names even when a local forwarding resolver is used on a loopback address, `dockerd` detects this scenario and instead forward DNS requests from the host namework namespace. The loopback resolver then forwards the requests to its configured upstream resolvers, as expected. Because `dockerd` forwards DNS requests to the host loopback device, bypassing the container network namespace's normal routing semantics entirely, internal networks can unexpectedly forward DNS requests to an external nameserver. By registering a domain for which they control the authoritative nameservers, an attacker could arrange for a compromised container to exfiltrate data by encoding it in DNS queries that will eventually be answered by their nameservers. Docker Desktop is not affected, as Docker Desktop always runs an internal resolver on a RFC 1918 address. Moby releases 26.0.0, 25.0.4, and 23.0.11 are patched to prevent forwarding any DNS requests from internal networks. As a workaround, run containers intended to be solely attached to internal networks with a custom upstream address, which will force all upstream DNS queries to be resolved from the container's network namespace.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.8% (unchanged from 0.7% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 56th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2024-03-28. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-669 Incorrect Resource Transfer Between Spheres
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-29018 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-29018?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-29018?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-29018 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
mobyproject:mobybefore 23.0.11
mobyproject:mobyfrom 24.0.0 before 25.0.5
mobyproject:moby26.0.0:rc1
mobyproject:moby26.0.0:rc2
mobyproject:moby26.0.0:rc3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-mq39-4gv4-mvpxGogithub.com/docker/docker>=26.0.0-rc1 <26.0.0-rc326.0.0-rc3
GHSA-mq39-4gv4-mvpxGogithub.com/docker/docker>=25.0.0 <25.0.525.0.5
GHSA-mq39-4gv4-mvpxGogithub.com/docker/docker<23.0.1123.0.11
GO-2024-2659Gogithub.com/docker/docker>=25.0.0+incompatible <25.0.5+incompatible
>=26.0.0-rc1+incompatible <26.0.0-rc3+incompatible
25.0.5+incompatible, 26.0.0-rc3+incompatible

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12docker.iono fix listedDEBIAN-CVE-2024-29018
Debian13, 14docker.io26.1.4+dfsg1-9DEBIAN-CVE-2024-29018
Ubuntu22.04:LTSdocker.io-app27.5.1-0ubuntu3~22.04.2UBUNTU-CVE-2024-29018
Ubuntu22.04:LTS, 24.04:LTS, Pro:20.04:LTSdocker.iono fix listedUBUNTU-CVE-2024-29018
Ubuntu24.04:LTSdocker.io-app27.5.1-0ubuntu3~24.04.2UBUNTU-CVE-2024-29018
UbuntuPro:16.04:LTSdocker.io18.09.7-0ubuntu1~16.04.9+esm2UBUNTU-CVE-2024-29018 USN-7161-2
UbuntuPro:18.04:LTSdocker.io20.10.21-0ubuntu1~18.04.3+esm2UBUNTU-CVE-2024-29018 USN-7161-1 USN-7161-2
UbuntuPro:20.04:LTSdocker.io-app26.1.3-0ubuntu1~20.04.1+esm1UBUNTU-CVE-2024-29018 USN-7161-2
UbuntuPro:22.04:LTSdocker.io-app26.1.3-0ubuntu1~22.04.1+esm1UBUNTU-CVE-2024-29018 USN-7161-2
UbuntuPro:24.04:LTSdocker.io-app26.1.3-0ubuntu1~24.04.1+esm1UBUNTU-CVE-2024-29018 USN-7161-1
SUSEEnterprise Storage 7.1, Linux Enterprise High Performance Computing 15 SP3-LTSS, Linux Enterprise High Performance Computing 15 SP4-ESPOS and 15 moredocker27.5.1_ce-150000.218.1SUSE-SU-2025:1062-1
SUSEEnterprise Storage 7.1, Linux Enterprise High Performance Computing 15 SP3-LTSS, Linux Enterprise High Performance Computing 15 SP4-ESPOS and 11 moredocker-stable24.0.9_ce-150000.1.25.1SUSE-SU-2025:03545-1
SUSEEnterprise Storage 7.1, Linux Enterprise High Performance Computing 15 SP3-LTSS, Linux Enterprise High Performance Computing 15 SP4-ESPOS and 10 moredocker-stable24.0.9_ce-150000.1.15.1SUSE-SU-2025:1062-1
SUSELinux Enterprise Micro 5.1, Linux Enterprise Micro 5.2, Linux Enterprise Micro 5.3 and 3 moredocker27.5.1_ce-150000.215.3SUSE-SU-2025:0776-1
SUSELinux Enterprise Module for Containers 15 SP6docker-stable24.0.9_ce-150000.1.11.1SUSE-SU-2025:0226-1
SUSELinux Enterprise Module for Containers 15 SP7docker-stable24.0.9_ce-150000.1.39.1SUSE-SU-2026:0972-1
SUSELinux Enterprise Server 12 SP5-LTSS, Linux Enterprise Server LTSS Extended Security 12 SP5docker27.5.1_ce-98.126.1SUSE-SU-2025:1102-1
SUSELinux Enterprise Server 12 SP5-LTSS, Linux Enterprise Server LTSS Extended Security 12 SP5docker-stable24.0.9_ce-1.11.1SUSE-SU-2025:1102-1
SUSELinux Enterprise Server 12 SP5-LTSS, Linux Enterprise Server LTSS Extended Security 12 SP5docker-stable24.0.9_ce-1.20.1SUSE-SU-2025:03540-1
SUSELinux Enterprise Server LTSS Extended Security 12 SP5docker27.5.1_ce-98.123.1SUSE-SU-2025:0992-1
SUSELinux Enterprise Server LTSS Extended Security 12 SP5docker-stable24.0.9_ce-1.32.1SUSE-SU-2026:1118-1
SUSELinux Micro 6.0docker27.5.1_ce-2.1SUSE-SU-2025:20205-1
1 more for SUSE in the JSON and on SUSE's page.
openSUSELeap 15.6docker27.5.1_ce-150000.215.3SUSE-SU-2025:0776-1
openSUSELeap 15.6docker27.5.1_ce-150000.218.1SUSE-SU-2025:1062-1
openSUSELeap 15.6docker-stable24.0.9_ce-150000.1.11.1SUSE-SU-2025:0226-1
openSUSELeap 15.6docker-stable24.0.9_ce-150000.1.15.1SUSE-SU-2025:1062-1
openSUSELeap 15.6docker-stable24.0.9_ce-150000.1.25.1SUSE-SU-2025:03545-1
openSUSELeap 15.6docker-stable24.0.9_ce-150000.1.39.1SUSE-SU-2026:0972-1
openSUSETumbleweeddocker27.4.1_ce-12.1openSUSE-SU-2024:14597-1
openSUSETumbleweeddocker-stable24.0.9_ce-6.1openSUSE-SU-2024:14598-1
Alpinev3.18docker25.0.2-r0ALPINE-CVE-2024-29018
Alpinev3.19docker25.0.5-r0ALPINE-CVE-2024-29018
Alpinev3.20, v3.21, v3.22 and 2 moredocker26.0.0-r0ALPINE-CVE-2024-29018
Azure Linux2moby-engine24.0.9-9AZL-40034
Azure Linux3moby-engine25.0.3-6AZL-36900
Alpaquita23dockerno fix listedBELL-CVE-2024-29018
Alpaquitastreamdocker26.0.0-r0BELL-CVE-2024-29018

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpine · Alpaquita.

Red Hat

Red Hat rates this Moderate.

ProductPackageStateAdvisory
Red Hat Migration Toolkit for Containers 1.8rhmtc/openshift-migration-controller-rhel8:v1.8.4-22Fixed 2024-09-26RHSA-2024:7164
Builds for Red Hat OpenShiftopenshift-builds/openshift-builds-waiters-rhel8Not affected
cert-manager Operator for Red Hat OpenShiftcert-manager/jetstack-cert-manager-rhel9Not affected
Logging Subsystem for Red Hat OpenShiftopenshift-logging/logging-loki-rhel9Not affected
Migration Toolkit for Applications 6mta/mta-hub-rhel9Not affected
Migration Toolkit for Applications 6mta/mta-windup-addon-rhel9Not affected
Migration Toolkit for Containersrhmtc/openshift-velero-plugin-rhel8Not affected
Multicluster Engine for Kubernetesmulticluster-engine/agent-service-rhel8Not affected
Multicluster Engine for Kubernetesmulticluster-engine/assisted-installer-agent-rhel8Not affected
Multicluster Engine for Kubernetesmulticluster-engine/assisted-installer-rhel8Not affected
Multicluster Engine for Kubernetesmulticluster-engine/cluster-api-provider-aws-rhel9Not affected
Multicluster Engine for Kubernetesmulticluster-engine/cluster-api-provider-azure-rhel8Not affected
OpenShift API for Data Protectionoadp/oadp-kubevirt-velero-plugin-rhel8Not affected
OpenShift API for Data Protectionoadp/oadp-rhel8-operatorNot affected
OpenShift API for Data Protectionoadp/oadp-velero-plugin-rhel9Not affected
OpenShift Developer Tools and Servicesocp-tools-4/jenkins-rhel8Not affected
OpenShift Serverlessopenshift-serverless-1/client-kn-rhel8Not affected
OpenShift Serverlessopenshift-serverless-1/serving-queue-rhel8Not affected
OpenShift Service Mesh 2openshift-service-mesh/istio-cni-rhel8Not affected
OpenShift Service Mesh 2openshift-service-mesh/istio-rhel8-operatorNot affected
86 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2024-29018.

References

Check your stackJSON