MediumGHSA-33pg-m6jh-5237CVE-2023-28841GO-2023-1700

Docker Swarm encrypted overlay network traffic may be unencrypted

Published 4 Apr 2023 · Updated 10 Sept 2026

Is your project on an affected github.com/docker/docker?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=1.12.0 <20.10.24
Fixed in
20.10.24
Update to the fixed version for your release line, for example:go get github.com/docker/docker@v20.10.24
Affected
>=23.0.0 <23.0.3
Fixed in
23.0.3
Update to the fixed version for your release line, for example:go get github.com/docker/docker@v23.0.3

Details

Moby is an open source container framework developed by Docker Inc. that is distributed as Docker, Mirantis Container Runtime, and various other downstream projects/products. The Moby daemon component (dockerd), which is developed as moby/moby is commonly referred to as *Docker*.

Swarm Mode, which is compiled in and delivered by default in dockerd and is thus present in most major Moby downstreams, is a simple, built-in container orchestrator that is implemented through a combination of SwarmKit and supporting network code.

The overlay network driver is a core feature of Swarm Mode, providing isolated virtual LANs that allow communication between containers and services across the cluster. This driver is an implementation/user of VXLAN, which encapsulates link-layer (Ethernet) frames in UDP datagrams that tag the frame with a VXLAN Network ID (VNI) that identifies the originating overlay network. In addition, the overlay network driver supports an optional, off-by-default encrypted mode, which is especially useful when VXLAN packets traverses an untrusted network between nodes.

Encrypted overlay networks function by encapsulating the VXLAN datagrams through the use of the IPsec Encapsulating Security Payload protocol in Transport mode. By deploying IPSec encapsulation, encrypted overlay networks gain the additional properties of source authentication through cryptographic proof, data integrity through check-summing, and confidentiality through encryption.

When setting an endpoint up on an encrypted overlay network, Moby installs three iptables (Linux kernel firewall) rules that enforce both incoming and outgoing IPSec. These rules rely on the u32 iptables extension provided by the xt_u32 kernel module to directly filter on a VXLAN packet's VNI field, so that IPSec guarantees can be enforced on encrypted overlay networks without interfering with other overlay networks or other users of VXLAN.

An iptables rule designates outgoing VXLAN datagrams with a VNI that corresponds to an encrypted overlay network for IPsec encapsulation.

On Red Hat Enterprise Linux and derivatives such as CentOS and Rocky, the xt_u32 module has been:

This rule is not created when xt_u32 is unavailable, even though the container is still attached to the network.

Impact

Encrypted overlay networks on affected platforms silently transmit unencrypted data. As a result, overlay networks may appear to be functional, passing traffic as expected, but without any of the expected confidentiality or data integrity guarantees.

It is possible for an attacker sitting in a trusted position on the network to read all of the application traffic that is moving across the overlay network, resulting in unexpected secrets or user data disclosure. Thus, because many database protocols, internal APIs, etc. are not protected by a second layer of encryption, a user may rely on Swarm encrypted overlay networks to provide confidentiality, which due to this vulnerability is no longer guaranteed.

Patches

Patches are available in Moby releases 23.0.3, and 20.10.24. As Mirantis Container Runtime's 20.10 releases are numbered differently, users of that platform should update to 20.10.16.

Workarounds

  • Close the VXLAN port (by default, UDP port 4789) to outgoing traffic at the Internet boundary (see GHSA-vwm3-crmr-xfxw) in order to prevent unintentionally leaking unencrypted traffic over the Internet.
  • Ensure that the xt_u32 kernel module is available on all nodes of the Swarm cluster.

Background

  • #43382 partially discussed this concern, but did not consider the security implications.
  • Mirantis FIELD-5788 essentially duplicates #43382, and was created six months earlier; it similarly overlooked the security implications.
  • #45118 is the ancestor of the final patches, and was where the security implications were discovered.

Related

Is GHSA-33pg-m6jh-5237 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/docker/docker, and gives you the command that fixes it.

More advisories for github.com/docker/docker

  • LowCVE-2026-41568Race condition in 'docker cp' in github.com/docker/docker allows creation of arbitrary files · 25 Jun 2026
  • LowCVE-2026-41567Docker: 'PUT /containers/{id}/archive' executes container binary on the host in github.com/docker/docker · 25 Jun 2026
  • LowCVE-2026-42306Race condition in 'docker cp' in github.com/docker/docker allows bind mount redirection · 25 Jun 2026
  • HighCVE-2026-42306Docker: Race condition in docker cp allows bind mount redirection to host path · 18 May 2026
  • MediumCVE-2026-41568Docker: Race condition in docker cp allows creation of arbitrary empty files on the host via symlink swap · 18 May 2026
  • HighCVE-2026-41567Docker: `PUT /containers/{id}/archive` executes container binary on the host · 18 May 2026
All 66 advisories for github.com/docker/docker

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.