# CVE-2024-32473: Moby IPv6 enabled on IPv4-only network interfaces > Moby fails to disable IPv6 on IPv4-only networks, exposing containers to local network attacks via link-local addresses and multicast groups. - **Severity:** Medium 4.7 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 18 Apr 2024 - **Updated:** 21 Aug 2024 - **Also known as:** BELL-CVE-2024-32473, CLEANSTART-2026-OK96613, DEBIAN-CVE-2024-32473, GHSA-x84c-p2g9-rqv9, GO-2024-2737, OESA-2024-1591, OESA-2024-1625, UBUNTU-CVE-2024-32473 ## What is CVE-2024-32473? CVE-2024-32473 is a medium-severity vulnerability in moby, published on 18 Apr 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description 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. In 26.0.0, IPv6 is not disabled on network interfaces, including those belonging to networks where `--ipv6=false`. An container with an `ipvlan` or `macvlan` interface will normally be configured to share an external network link with the host machine. Because of this direct access, (1) Containers may be able to communicate with other hosts on the local network over link-local IPv6 addresses, (2) if router advertisements are being broadcast over the local network, containers may get SLAAC-assigned addresses, and (3) the interface will be a member of IPv6 multicast groups. This means interfaces in IPv4-only networks present an unexpectedly and unnecessarily increased attack surface. The issue is patched in 26.0.2. To completely disable IPv6 in a container, use `--sysctl=net.ipv6.conf.all.disable_ipv6=1` in the `docker create` or `docker run` command. Or, in the service configuration of a `compose` file. Weakness: CWE-668 (Exposure of Resource to Wrong Sphere) ## Which versions are affected by CVE-2024-32473? 3 open source packages ship an affected version, including github.com/docker/docker. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/docker/docker` | Go | From 26.0.0 | 26.0.2 | | `github.com/docker/docker` | Go | From 26.0.0 | 26.0.2 | | `github.com/docker/docker` | Go | From 26.0.0+incompatible | 26.0.2+incompatible | Products: Mobyproject Moby. ## How do I fix CVE-2024-32473? Upgrade github.com/docker/docker to a fixed version for your release line: 26.0.2 or 26.0.2+incompatible. ## Is CVE-2024-32473 being exploited? There is no known exploitation of CVE-2024-32473 in the wild and no public exploit code. ## Other vulnerabilities in moby - [CVE-2024-36623](https://insights.sbomify.com/CVE-2024-36623/): Moby Race Condition vulnerability (high 8.1) - [CVE-2023-28840](https://insights.sbomify.com/CVE-2023-28840/): moby/moby's dockerd daemon encrypted overlay network may be unauthenticated (high 7.5) - [CVE-2018-12608](https://insights.sbomify.com/CVE-2018-12608/): Docker Authentication Bypass (high 7.5) - [CVE-2024-24557](https://insights.sbomify.com/CVE-2024-24557/): Moby classic builder cache poisoning (medium 6.9) - [CVE-2023-28841](https://insights.sbomify.com/CVE-2023-28841/): moby/moby's dockerd daemon encrypted overlay network traffic may be unencrypted (medium 6.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-32473 and fix it if it is affected. What it is: CVE-2024-32473 is a medium-severity vulnerability in moby, published on 18 Apr 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2024-32473 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/docker/docker (Go): affected from 26.0.0; fixed in 26.0.2 - github.com/docker/docker (Go): affected from 26.0.0; fixed in 26.0.2 - github.com/docker/docker (Go): affected from 26.0.0+incompatible; fixed in 26.0.2+incompatible Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-32473/ (Markdown: https://insights.sbomify.com/CVE-2024-32473/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-32473 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-32473 - OSV: https://osv.dev/vulnerability/CVE-2024-32473 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-32473/ Summaries are generated and may contain mistakes; the official description above is the record.