{"id":"CVE-2023-28840","aliases":["ALPINE-CVE-2023-28840","BELL-CVE-2023-28840","DEBIAN-CVE-2023-28840","EUVD-2023-1150","GHSA-232p-vwff-86mp","GO-2023-1699","MGASA-2023-0329","OESA-2023-1238","SUSE-SU-2023:3307-1","SUSE-SU-2023:3536-1","SUSE-SU-2025:03540-1","SUSE-SU-2025:03545-1","UBUNTU-CVE-2023-28840","USN-7474-1","openSUSE-SU-2024:12876-1","openSUSE-SU-2024:13005-1","openSUSE-SU-2024:13205-1","openSUSE-SU-2025:15589-1"],"status":"published","title":"moby/moby's dockerd daemon encrypted overlay network may be unauthenticated","description":"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*.\n\nSwarm 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.\n\nThe 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.\n\nEncrypted 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.\n\nWhen 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.\n\nTwo iptables rules serve to filter incoming VXLAN datagrams with a VNI that corresponds to an encrypted network and discards unencrypted datagrams. The rules are appended to the end of the INPUT filter chain, following any rules that have been previously set by the system administrator. Administrator-set rules take precedence over the rules Moby sets to discard unencrypted VXLAN datagrams, which can potentially admit unencrypted datagrams that should have been discarded.\n\nThe injection of arbitrary Ethernet frames can enable a Denial of Service attack. A sophisticated attacker may be able to establish a UDP or TCP connection by way of the container’s outbound gateway that would otherwise be blocked by a stateful firewall, or carry out other escalations beyond simple injection by smuggling packets into the overlay network.\n\nPatches 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.\n\nSome workarounds are available. Close the VXLAN port (by default, UDP port 4789) to incoming traffic at the Internet boundary to prevent all VXLAN packet injection, and/or ensure that the `xt_u32` kernel module is available on all nodes of the Swarm cluster.","severity":{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:L","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-09","score":0.02559,"percentile":0.85198,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-203","CWE-420","CWE-636","CWE-755"],"published":"2023-04-04T21:13:03Z","modified":"2026-11-03T06:32:48Z","fixes":[{"ecosystem":"Go","package":"github.com/docker/docker","fixed_in":["20.10.24","23.0.3","20.10.24+incompatible","23.0.3+incompatible"],"sources":["ghsa","osv"]},{"ecosystem":"Alpine:v3.17","package":"docker","fixed_in":["20.10.24-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.18","package":"docker","fixed_in":["23.0.3-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.19","package":"docker","fixed_in":["23.0.3-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.20","package":"docker","fixed_in":["23.0.3-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.21","package":"docker","fixed_in":["23.0.3-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.22","package":"docker","fixed_in":["23.0.3-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.23","package":"docker","fixed_in":["23.0.3-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.24","package":"docker","fixed_in":["23.0.3-r0"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"docker.io","fixed_in":["20.10.24+dfsg1-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"docker.io","fixed_in":["20.10.24+dfsg1-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"docker.io","fixed_in":["20.10.24+dfsg1-1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"docker.io","fixed_in":["20.10.21-0ubuntu1~18.04.3+esm3"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"docker.io","fixed_in":["20.10.21-0ubuntu1~20.04.6+esm2"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:22.04:LTS","package":"docker.io","fixed_in":["20.10.21-0ubuntu1~22.04.7+esm2"],"sources":["osv"]},{"ecosystem":"openSUSE:Tumbleweed","package":"docker-compose","fixed_in":["2.17.3-1.1"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"Go","package":"github.com/docker/docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.12.0"},{"fixed":"20.10.24"}]}]},{"source":"ghsa","ecosystem":"Go","package":"github.com/docker/docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"23.0.0"},{"fixed":"23.0.3"}]}]},{"source":"osv","ecosystem":"Alpine:v3.17","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20.10.24-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.18","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"23.0.3-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.19","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"23.0.3-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.20","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"23.0.3-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.21","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"23.0.3-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.22","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"23.0.3-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.23","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"23.0.3-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.24","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"23.0.3-r0"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"docker.io","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20.10.24+dfsg1-1"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"docker.io","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20.10.24+dfsg1-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"docker.io","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20.10.24+dfsg1-1"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/docker/docker","ranges":[{"type":"SEMVER","events":[{"introduced":"1.12.0"},{"fixed":"20.10.24"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/docker/docker","ranges":[{"type":"SEMVER","events":[{"introduced":"23.0.0"},{"fixed":"23.0.3"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/docker/docker","ranges":[{"type":"SEMVER","events":[{"introduced":"1.12.0"},{"fixed":"20.10.24+incompatible"},{"introduced":"23.0.0+incompatible"},{"fixed":"23.0.3+incompatible"}]}]},{"source":"osv","ecosystem":"Mageia:9","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.5-4.mga9"}]}],"bundled":4},{"source":"osv","ecosystem":"Mageia:9","package":"docker-containerd","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.7.3-1.mga9"}]}],"bundled":4},{"source":"osv","ecosystem":"openEuler:20.03-LTS-SP1","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"engine-18.09.0-253.oe1"}]}],"bundled":3},{"source":"osv","ecosystem":"openEuler:20.03-LTS-SP3","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"engine-18.09.0-253.oe1"}]}],"bundled":3},{"source":"osv","ecosystem":"openEuler:22.03-LTS","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"engine-18.09.0-323.oe2203sp1"}]}],"bundled":3},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP1","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"engine-18.09.0-323.oe2203sp1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Containers 12","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20.10.25_ce-98.93.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.3","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.5_ce-150000.185.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.4","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.5_ce-150000.185.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Containers 15 SP4","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.5_ce-150000.185.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Containers 15 SP5","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.5_ce-150000.185.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.5_ce-150000.185.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.5_ce-150000.185.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-ESPOS","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.5_ce-150000.185.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.5_ce-150000.185.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP1-LTSS","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.5_ce-150000.185.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.5_ce-150000.185.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.5_ce-150000.185.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP1","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.5_ce-150000.185.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.5_ce-150000.185.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.5_ce-150000.185.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.1","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.5_ce-150000.185.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.2","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.5_ce-150000.185.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.5_ce-150000.185.1"}]}],"bundled":3},{"source":"osv","ecosystem":"openSUSE:Leap 15.4","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.5_ce-150000.185.1"}]}],"bundled":3},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.5_ce-150000.185.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"docker-stable","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.9_ce-1.20.1"}]}],"bundled":53},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"docker-stable","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.9_ce-1.20.1"}]}],"bundled":53},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Containers 15 SP6","package":"docker-stable","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.9_ce-150000.1.25.1"}]}],"bundled":53},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Containers 15 SP7","package":"docker-stable","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.9_ce-150000.1.25.1"}]}],"bundled":53},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"docker-stable","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.9_ce-150000.1.25.1"}]}],"bundled":53},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"docker-stable","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.9_ce-150000.1.25.1"}]}],"bundled":53},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"docker-stable","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.9_ce-150000.1.25.1"}]}],"bundled":53},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"docker-stable","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.9_ce-150000.1.25.1"}]}],"bundled":53},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"docker-stable","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.9_ce-150000.1.25.1"}]}],"bundled":53},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"docker-stable","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.9_ce-150000.1.25.1"}]}],"bundled":53},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"docker-stable","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.9_ce-150000.1.25.1"}]}],"bundled":53},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"docker-stable","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.9_ce-150000.1.25.1"}]}],"bundled":53},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"docker-stable","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.9_ce-150000.1.25.1"}]}],"bundled":53},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"docker-stable","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.9_ce-150000.1.25.1"}]}],"bundled":53},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"docker-stable","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.9_ce-150000.1.25.1"}]}],"bundled":53},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"docker-stable","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.9_ce-150000.1.25.1"}]}],"bundled":53},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"docker-stable","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.9_ce-150000.1.25.1"}]}],"bundled":53},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"docker.io","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.6.2~dfsg1-1ubuntu4","1.10.2-0ubuntu3","1.10.2-0ubuntu4","1.10.3-0ubuntu1","1.10.3-0ubuntu4","1.10.3-0ubuntu5","1.10.3-0ubuntu6","1.11.2-0ubuntu5~16.04","1.12.1-0ubuntu13~16.04.1","1.12.3-0ubuntu4~16.04.2","1.12.6-0ubuntu1~16.04.1","1.13.1-0ubuntu1~16.04.2","17.03.2-0ubuntu2~16.04.1","18.06.1-0ubuntu1~16.04.2","18.06.1-0ubuntu1.2~16.04.1","18.09.2-0ubuntu1~16.04.1","18.09.5-0ubuntu1~16.04.2","18.09.7-0ubuntu1~16.04.1","18.09.7-0ubuntu1~16.04.4","18.09.7-0ubuntu1~16.04.5","18.09.7-0ubuntu1~16.04.6","18.09.7-0ubuntu1~16.04.7","18.09.7-0ubuntu1~16.04.9+esm1","18.09.7-0ubuntu1~16.04.9+esm2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"docker.io","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20.10.21-0ubuntu1~18.04.3+esm3"}]}],"versions":["1.13.1-0ubuntu6","17.03.2-0ubuntu1","17.03.2-0ubuntu3","17.03.2-0ubuntu5","17.12.1-0ubuntu1","18.06.1-0ubuntu1~18.04.1","18.06.1-0ubuntu1.2~18.04.1","18.09.2-0ubuntu1~18.04.1","18.09.5-0ubuntu1~18.04.2","18.09.7-0ubuntu1~18.04.1","18.09.7-0ubuntu1~18.04.3","18.09.7-0ubuntu1~18.04.4","19.03.6-0ubuntu1~18.04.1","19.03.6-0ubuntu1~18.04.2","19.03.6-0ubuntu1~18.04.3","20.10.2-0ubuntu1~18.04.2","20.10.2-0ubuntu1~18.04.3","20.10.7-0ubuntu1~18.04.1","20.10.7-0ubuntu1~18.04.2","20.10.7-0ubuntu5~18.04.2","20.10.7-0ubuntu5~18.04.3","20.10.12-0ubuntu2~18.04.1","20.10.21-0ubuntu1~18.04.2","20.10.21-0ubuntu1~18.04.3","20.10.21-0ubuntu1~18.04.3+esm1","20.10.21-0ubuntu1~18.04.3+esm2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"docker.io","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20.10.21-0ubuntu1~20.04.6+esm2"}]}],"versions":["19.03.2-0ubuntu1","19.03.6-0ubuntu1","19.03.8-0ubuntu1","19.03.8-0ubuntu1.20.04","19.03.8-0ubuntu1.20.04.1","19.03.8-0ubuntu1.20.04.2","20.10.2-0ubuntu1~20.04.2","20.10.2-0ubuntu1~20.04.3","20.10.7-0ubuntu1~20.04.1","20.10.7-0ubuntu1~20.04.2","20.10.7-0ubuntu5~20.04.1","20.10.7-0ubuntu5~20.04.2","20.10.12-0ubuntu2~20.04.1","20.10.21-0ubuntu1~20.04.1","20.10.21-0ubuntu1~20.04.2","20.10.21-0ubuntu1~20.04.4","20.10.21-0ubuntu1~20.04.5","20.10.21-0ubuntu1~20.04.6","20.10.21-0ubuntu1~20.04.6+esm1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"docker.io-app","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["20.10.25-0ubuntu1~20.04.1","20.10.25-0ubuntu1~20.04.2","24.0.5-0ubuntu1~20.04.1","24.0.7-0ubuntu2~20.04.1","26.1.3-0ubuntu1~20.04.1","26.1.3-0ubuntu1~20.04.1+esm1","26.1.3-0ubuntu1~20.04.1+esm2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:22.04:LTS","package":"docker.io","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20.10.21-0ubuntu1~22.04.7+esm2"}]}],"versions":["20.10.7-0ubuntu5","20.10.7-0ubuntu7","20.10.12-0ubuntu1","20.10.12-0ubuntu2","20.10.12-0ubuntu3","20.10.12-0ubuntu3+gke1.24.1","20.10.12-0ubuntu4","20.10.21-0ubuntu1~22.04.2","20.10.21-0ubuntu1~22.04.3","20.10.21-0ubuntu1~22.04.5","20.10.21-0ubuntu1~22.04.6","20.10.21-0ubuntu1~22.04.7","20.10.21-0ubuntu1~22.04.7+esm1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:22.04:LTS","package":"docker.io-app","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["20.10.25-0ubuntu1~22.04.1","20.10.25-0ubuntu1~22.04.2","24.0.5-0ubuntu1~22.04.1","24.0.7-0ubuntu2~22.04.1","26.1.3-0ubuntu1~22.04.1","26.1.3-0ubuntu1~22.04.1+esm1","27.5.1-0ubuntu3~22.04.1","27.5.1-0ubuntu3~22.04.2","28.2.2-0ubuntu1~22.04.1","29.1.3-0ubuntu3~22.04.1","29.1.3-0ubuntu3~22.04.2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"docker.io","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20.10.21-0ubuntu1~18.04.3+esm3"}]}],"versions":["1.13.1-0ubuntu6","17.03.2-0ubuntu1","17.03.2-0ubuntu3","17.03.2-0ubuntu5","17.12.1-0ubuntu1","18.06.1-0ubuntu1~18.04.1","18.06.1-0ubuntu1.2~18.04.1","18.09.2-0ubuntu1~18.04.1","18.09.5-0ubuntu1~18.04.2","18.09.7-0ubuntu1~18.04.1","18.09.7-0ubuntu1~18.04.3","18.09.7-0ubuntu1~18.04.4","19.03.6-0ubuntu1~18.04.1","19.03.6-0ubuntu1~18.04.2","19.03.6-0ubuntu1~18.04.3","20.10.2-0ubuntu1~18.04.2","20.10.2-0ubuntu1~18.04.3","20.10.7-0ubuntu1~18.04.1","20.10.7-0ubuntu1~18.04.2","20.10.7-0ubuntu5~18.04.2","20.10.7-0ubuntu5~18.04.3","20.10.12-0ubuntu2~18.04.1","20.10.21-0ubuntu1~18.04.2","20.10.21-0ubuntu1~18.04.3","20.10.21-0ubuntu1~18.04.3+esm1","20.10.21-0ubuntu1~18.04.3+esm2"],"bundled":7},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"docker.io","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20.10.21-0ubuntu1~20.04.6+esm2"}]}],"versions":["19.03.2-0ubuntu1","19.03.6-0ubuntu1","19.03.8-0ubuntu1","19.03.8-0ubuntu1.20.04","19.03.8-0ubuntu1.20.04.1","19.03.8-0ubuntu1.20.04.2","20.10.2-0ubuntu1~20.04.2","20.10.2-0ubuntu1~20.04.3","20.10.7-0ubuntu1~20.04.1","20.10.7-0ubuntu1~20.04.2","20.10.7-0ubuntu5~20.04.1","20.10.7-0ubuntu5~20.04.2","20.10.12-0ubuntu2~20.04.1","20.10.21-0ubuntu1~20.04.1","20.10.21-0ubuntu1~20.04.2","20.10.21-0ubuntu1~20.04.4","20.10.21-0ubuntu1~20.04.5","20.10.21-0ubuntu1~20.04.6","20.10.21-0ubuntu1~20.04.6+esm1"],"bundled":7},{"source":"osv","ecosystem":"Ubuntu:Pro:22.04:LTS","package":"docker.io","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20.10.21-0ubuntu1~22.04.7+esm2"}]}],"versions":["20.10.7-0ubuntu5","20.10.7-0ubuntu7","20.10.12-0ubuntu1","20.10.12-0ubuntu2","20.10.12-0ubuntu3","20.10.12-0ubuntu3+gke1.24.1","20.10.12-0ubuntu4","20.10.21-0ubuntu1~22.04.2","20.10.21-0ubuntu1~22.04.3","20.10.21-0ubuntu1~22.04.5","20.10.21-0ubuntu1~22.04.6","20.10.21-0ubuntu1~22.04.7","20.10.21-0ubuntu1~22.04.7+esm1"],"bundled":7},{"source":"osv","ecosystem":"Ubuntu:Pro:24.04:LTS","package":"docker.io","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20.10.25+dfsg1-2ubuntu1+esm2"}]}],"versions":["20.10.24+dfsg1-1ubuntu2","20.10.25+dfsg1-2ubuntu1","20.10.25+dfsg1-2ubuntu1+esm1"],"bundled":7},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"docker-compose","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.17.3-1.1"}]}]},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"kubescape","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.3.6-1.1"}]}],"bundled":2},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"docker","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.5_ce-2.1"}]}],"bundled":3},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"docker-stable","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.9_ce-15.1"}]}],"bundled":43}],"products":[{"vendor":"moby","product":"moby"},{"vendor":"mobyproject","product":"moby"}],"references":[{"url":"https://github.com/moby/moby/security/advisories/GHSA-232p-vwff-86mp","tags":["x_refsource_CONFIRM","x_transferred","Mitigation","Vendor Advisory","advisory","web","report"]},{"url":"https://github.com/moby/libnetwork/security/advisories/GHSA-gvm4-2qqg-m333","tags":["x_refsource_MISC","x_transferred","Vendor Advisory","advisory","web","report"]},{"url":"https://github.com/moby/moby/security/advisories/GHSA-33pg-m6jh-5237","tags":["x_refsource_MISC","x_transferred","Not Applicable","advisory","web","report"]},{"url":"https://github.com/moby/moby/security/advisories/GHSA-6wrf-mxfj-pf5p","tags":["x_refsource_MISC","x_transferred","Not Applicable","advisory","web","report"]},{"url":"https://github.com/moby/moby/security/advisories/GHSA-vwm3-crmr-xfxw","tags":["x_refsource_MISC","x_transferred","Vendor Advisory","advisory","web","report"]},{"url":"https://github.com/moby/moby/issues/43382","tags":["x_refsource_MISC","x_transferred","Exploit","Issue Tracking","Third Party Advisory","report","web"]},{"url":"https://github.com/moby/moby/pull/45118","tags":["x_refsource_MISC","x_transferred","Issue Tracking","Patch","fix","web","report"]},{"url":"https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZTE4ITXXPIWZEQ4HYQCB6N6GZIMWXDAI/","tags":["x_transferred","web"]},{"url":"https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LYZOKMMVX4SIEHPJW3SJUQGMO5YZCPHC/","tags":["x_transferred","web"]},{"url":"https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XNF4OLYZRQE75EB5TW5N42FSXHBXGWFE/","tags":["x_transferred","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-28840","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-232p-vwff-86mp"},{"url":"https://security.alpinelinux.org/vuln/CVE-2023-28840","tags":["advisory"]},{"url":"https://docs.bell-sw.com/security/cves/CVE-2023-28840","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/28xxx/CVE-2023-28840.json","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2023-28840","tags":["advisory"]},{"url":"https://github.com/moby/moby","tags":["package"]},{"url":"https://advisories.mageia.org/MGASA-2023-0329.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=31733","tags":["report"]},{"url":"https://github.com/moby/buildkit/security/advisories/GHSA-gc89-7gcr-jxqc","tags":["advisory"]},{"url":"https://github.com/moby/moby/releases/tag/v24.0.5","tags":["web"]},{"url":"https://github.com/moby/moby/releases/tag/v24.0.4","tags":["web"]},{"url":"https://github.com/moby/moby/releases/tag/v24.0.3","tags":["web"]},{"url":"https://github.com/moby/moby/releases/tag/v24.0.2","tags":["web"]},{"url":"https://github.com/moby/moby/releases/tag/v24.0.1","tags":["web"]},{"url":"https://github.com/moby/moby/releases/tag/v24.0.0","tags":["web"]},{"url":"https://github.com/moby/moby/releases/tag/v23.0.3","tags":["web"]},{"url":"https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2023-1238","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-28842","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-28841","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2023/suse-su-20233307-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1214107","tags":["report"]},{"url":"https://bugzilla.suse.com/1214108","tags":["report"]},{"url":"https://bugzilla.suse.com/1214109","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2023-28840","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-28841","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-28842","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2023/suse-su-20233536-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1210797","tags":["report"]},{"url":"https://bugzilla.suse.com/1212368","tags":["report"]},{"url":"https://bugzilla.suse.com/1213120","tags":["report"]},{"url":"https://bugzilla.suse.com/1213229","tags":["report"]},{"url":"https://bugzilla.suse.com/1213500","tags":["report"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202503540-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1001161","tags":["report"]},{"url":"https://bugzilla.suse.com/1004490","tags":["report"]},{"url":"https://bugzilla.suse.com/1007249","tags":["report"]},{"url":"https://bugzilla.suse.com/1009961","tags":["report"]},{"url":"https://bugzilla.suse.com/1012568","tags":["report"]},{"url":"https://bugzilla.suse.com/1015661","tags":["report"]},{"url":"https://bugzilla.suse.com/1016307","tags":["report"]},{"url":"https://bugzilla.suse.com/1016992","tags":["report"]},{"url":"https://bugzilla.suse.com/1019251","tags":["report"]},{"url":"https://bugzilla.suse.com/1020806","tags":["report"]},{"url":"https://bugzilla.suse.com/1021227","tags":["report"]},{"url":"https://bugzilla.suse.com/1026827","tags":["report"]},{"url":"https://bugzilla.suse.com/1028638","tags":["report"]},{"url":"https://bugzilla.suse.com/1028639","tags":["report"]},{"url":"https://bugzilla.suse.com/1029320","tags":["report"]},{"url":"https://bugzilla.suse.com/1029630","tags":["report"]},{"url":"https://bugzilla.suse.com/1030702","tags":["report"]},{"url":"https://bugzilla.suse.com/1032287","tags":["report"]},{"url":"https://bugzilla.suse.com/1032644","tags":["report"]},{"url":"https://bugzilla.suse.com/1034053","tags":["report"]},{"url":"https://bugzilla.suse.com/1034063","tags":["report"]},{"url":"https://bugzilla.suse.com/1037436","tags":["report"]},{"url":"https://bugzilla.suse.com/1037607","tags":["report"]},{"url":"https://bugzilla.suse.com/1038476","tags":["report"]},{"url":"https://bugzilla.suse.com/1038493","tags":["report"]},{"url":"https://bugzilla.suse.com/1045628","tags":["report"]},{"url":"https://bugzilla.suse.com/1046024","tags":["report"]},{"url":"https://bugzilla.suse.com/1047218","tags":["report"]},{"url":"https://bugzilla.suse.com/1048046","tags":["report"]},{"url":"https://bugzilla.suse.com/1051429","tags":["report"]},{"url":"https://bugzilla.suse.com/1055676","tags":["report"]},{"url":"https://bugzilla.suse.com/1057743","tags":["report"]},{"url":"https://bugzilla.suse.com/1058173","tags":["report"]},{"url":"https://bugzilla.suse.com/1059011","tags":["report"]},{"url":"https://bugzilla.suse.com/1064781","tags":["report"]},{"url":"https://bugzilla.suse.com/1065609","tags":["report"]},{"url":"https://bugzilla.suse.com/1066210","tags":["report"]},{"url":"https://bugzilla.suse.com/1066801","tags":["report"]},{"url":"https://bugzilla.suse.com/1069468","tags":["report"]},{"url":"https://bugzilla.suse.com/1069758","tags":["report"]},{"url":"https://bugzilla.suse.com/1072798","tags":["report"]},{"url":"https://bugzilla.suse.com/1073877","tags":["report"]},{"url":"https://bugzilla.suse.com/1074971","tags":["report"]},{"url":"https://bugzilla.suse.com/1080978","tags":["report"]},{"url":"https://bugzilla.suse.com/1084533","tags":["report"]},{"url":"https://bugzilla.suse.com/1085117","tags":["report"]},{"url":"https://bugzilla.suse.com/1085380","tags":["report"]},{"url":"https://bugzilla.suse.com/1086185","tags":["report"]},{"url":"https://bugzilla.suse.com/1089732","tags":["report"]},{"url":"https://bugzilla.suse.com/1095817","tags":["report"]},{"url":"https://bugzilla.suse.com/1096726","tags":["report"]},{"url":"https://bugzilla.suse.com/1099277","tags":["report"]},{"url":"https://bugzilla.suse.com/1100331","tags":["report"]},{"url":"https://bugzilla.suse.com/1100727","tags":["report"]},{"url":"https://bugzilla.suse.com/1102522","tags":["report"]},{"url":"https://bugzilla.suse.com/1104821","tags":["report"]},{"url":"https://bugzilla.suse.com/1105000","tags":["report"]},{"url":"https://bugzilla.suse.com/1108038","tags":["report"]},{"url":"https://bugzilla.suse.com/1112980","tags":["report"]},{"url":"https://bugzilla.suse.com/1113313","tags":["report"]},{"url":"https://bugzilla.suse.com/1114832","tags":["report"]},{"url":"https://bugzilla.suse.com/1115464","tags":["report"]},{"url":"https://bugzilla.suse.com/1118897","tags":["report"]},{"url":"https://bugzilla.suse.com/1118898","tags":["report"]},{"url":"https://bugzilla.suse.com/1118899","tags":["report"]},{"url":"https://bugzilla.suse.com/1118990","tags":["report"]},{"url":"https://bugzilla.suse.com/1119634","tags":["report"]},{"url":"https://bugzilla.suse.com/1121412","tags":["report"]},{"url":"https://bugzilla.suse.com/1121768","tags":["report"]},{"url":"https://bugzilla.suse.com/1122469","tags":["report"]},{"url":"https://bugzilla.suse.com/1124308","tags":["report"]},{"url":"https://bugzilla.suse.com/1128376","tags":["report"]},{"url":"https://bugzilla.suse.com/1128746","tags":["report"]},{"url":"https://bugzilla.suse.com/1134068","tags":["report"]},{"url":"https://bugzilla.suse.com/1138920","tags":["report"]},{"url":"https://bugzilla.suse.com/1139649","tags":["report"]},{"url":"https://bugzilla.suse.com/1142160","tags":["report"]},{"url":"https://bugzilla.suse.com/1142413","tags":["report"]},{"url":"https://bugzilla.suse.com/1143349","tags":["report"]},{"url":"https://bugzilla.suse.com/1150397","tags":["report"]},{"url":"https://bugzilla.suse.com/1153367","tags":["report"]},{"url":"https://bugzilla.suse.com/1157330","tags":["report"]},{"url":"https://bugzilla.suse.com/1158590","tags":["report"]},{"url":"https://bugzilla.suse.com/1170415","tags":["report"]},{"url":"https://bugzilla.suse.com/1170446","tags":["report"]},{"url":"https://bugzilla.suse.com/1172377","tags":["report"]},{"url":"https://bugzilla.suse.com/1174075","tags":["report"]},{"url":"https://bugzilla.suse.com/1175081","tags":["report"]},{"url":"https://bugzilla.suse.com/1176708","tags":["report"]},{"url":"https://bugzilla.suse.com/1178760","tags":["report"]},{"url":"https://bugzilla.suse.com/1178801","tags":["report"]},{"url":"https://bugzilla.suse.com/1180243","tags":["report"]},{"url":"https://bugzilla.suse.com/1180401","tags":["report"]},{"url":"https://bugzilla.suse.com/1181594","tags":["report"]},{"url":"https://bugzilla.suse.com/1181641","tags":["report"]},{"url":"https://bugzilla.suse.com/1181677","tags":["report"]},{"url":"https://bugzilla.suse.com/1181730","tags":["report"]},{"url":"https://bugzilla.suse.com/1181732","tags":["report"]},{"url":"https://bugzilla.suse.com/1182168","tags":["report"]},{"url":"https://bugzilla.suse.com/1182476","tags":["report"]},{"url":"https://bugzilla.suse.com/1182947","tags":["report"]},{"url":"https://bugzilla.suse.com/1183855","tags":["report"]},{"url":"https://bugzilla.suse.com/1184768","tags":["report"]},{"url":"https://bugzilla.suse.com/1188447","tags":["report"]},{"url":"https://bugzilla.suse.com/1190670","tags":["report"]},{"url":"https://bugzilla.suse.com/1191015","tags":["report"]},{"url":"https://bugzilla.suse.com/1191121","tags":["report"]},{"url":"https://bugzilla.suse.com/1191334","tags":["report"]},{"url":"https://bugzilla.suse.com/1191355","tags":["report"]},{"url":"https://bugzilla.suse.com/1191434","tags":["report"]},{"url":"https://bugzilla.suse.com/1192814","tags":["report"]},{"url":"https://bugzilla.suse.com/1193273","tags":["report"]},{"url":"https://bugzilla.suse.com/1193930","tags":["report"]},{"url":"https://bugzilla.suse.com/1197284","tags":["report"]},{"url":"https://bugzilla.suse.com/1197517","tags":["report"]},{"url":"https://bugzilla.suse.com/1200022","tags":["report"]},{"url":"https://bugzilla.suse.com/1200145","tags":["report"]},{"url":"https://bugzilla.suse.com/1205375","tags":["report"]},{"url":"https://bugzilla.suse.com/1206065","tags":["report"]},{"url":"https://bugzilla.suse.com/1208074","tags":["report"]},{"url":"https://bugzilla.suse.com/1210141","tags":["report"]},{"url":"https://bugzilla.suse.com/1211578","tags":["report"]},{"url":"https://bugzilla.suse.com/1215323","tags":["report"]},{"url":"https://bugzilla.suse.com/1217513","tags":["report"]},{"url":"https://bugzilla.suse.com/1219267","tags":["report"]},{"url":"https://bugzilla.suse.com/1219268","tags":["report"]},{"url":"https://bugzilla.suse.com/1219438","tags":["report"]},{"url":"https://bugzilla.suse.com/1240150","tags":["report"]},{"url":"https://bugzilla.suse.com/1247362","tags":["report"]},{"url":"https://bugzilla.suse.com/1250508","tags":["report"]},{"url":"https://bugzilla.suse.com/1250596","tags":["report"]},{"url":"https://bugzilla.suse.com/885209","tags":["report"]},{"url":"https://bugzilla.suse.com/907012","tags":["report"]},{"url":"https://bugzilla.suse.com/907014","tags":["report"]},{"url":"https://bugzilla.suse.com/908033","tags":["report"]},{"url":"https://bugzilla.suse.com/909709","tags":["report"]},{"url":"https://bugzilla.suse.com/909710","tags":["report"]},{"url":"https://bugzilla.suse.com/909712","tags":["report"]},{"url":"https://bugzilla.suse.com/913211","tags":["report"]},{"url":"https://bugzilla.suse.com/913213","tags":["report"]},{"url":"https://bugzilla.suse.com/920645","tags":["report"]},{"url":"https://bugzilla.suse.com/930235","tags":["report"]},{"url":"https://bugzilla.suse.com/931301","tags":["report"]},{"url":"https://bugzilla.suse.com/935570","tags":["report"]},{"url":"https://bugzilla.suse.com/938156","tags":["report"]},{"url":"https://bugzilla.suse.com/942369","tags":["report"]},{"url":"https://bugzilla.suse.com/942370","tags":["report"]},{"url":"https://bugzilla.suse.com/946653","tags":["report"]},{"url":"https://bugzilla.suse.com/949660","tags":["report"]},{"url":"https://bugzilla.suse.com/950931","tags":["report"]},{"url":"https://bugzilla.suse.com/953182","tags":["report"]},{"url":"https://bugzilla.suse.com/954737","tags":["report"]},{"url":"https://bugzilla.suse.com/954797","tags":["report"]},{"url":"https://bugzilla.suse.com/954812","tags":["report"]},{"url":"https://bugzilla.suse.com/956434","tags":["report"]},{"url":"https://bugzilla.suse.com/958255","tags":["report"]},{"url":"https://bugzilla.suse.com/959405","tags":["report"]},{"url":"https://bugzilla.suse.com/963142","tags":["report"]},{"url":"https://bugzilla.suse.com/964468","tags":["report"]},{"url":"https://bugzilla.suse.com/964673","tags":["report"]},{"url":"https://bugzilla.suse.com/965600","tags":["report"]},{"url":"https://bugzilla.suse.com/965918","tags":["report"]},{"url":"https://bugzilla.suse.com/968933","tags":["report"]},{"url":"https://bugzilla.suse.com/968972","tags":["report"]},{"url":"https://bugzilla.suse.com/970637","tags":["report"]},{"url":"https://bugzilla.suse.com/974208","tags":["report"]},{"url":"https://bugzilla.suse.com/976777","tags":["report"]},{"url":"https://bugzilla.suse.com/977394","tags":["report"]},{"url":"https://bugzilla.suse.com/978260","tags":["report"]},{"url":"https://bugzilla.suse.com/980555","tags":["report"]},{"url":"https://bugzilla.suse.com/983015","tags":["report"]},{"url":"https://bugzilla.suse.com/984942","tags":["report"]},{"url":"https://bugzilla.suse.com/987198","tags":["report"]},{"url":"https://bugzilla.suse.com/988408","tags":["report"]},{"url":"https://bugzilla.suse.com/988707","tags":["report"]},{"url":"https://bugzilla.suse.com/989566","tags":["report"]},{"url":"https://bugzilla.suse.com/993847","tags":["report"]},{"url":"https://bugzilla.suse.com/995058","tags":["report"]},{"url":"https://bugzilla.suse.com/995102","tags":["report"]},{"url":"https://bugzilla.suse.com/995620","tags":["report"]},{"url":"https://bugzilla.suse.com/996015","tags":["report"]},{"url":"https://bugzilla.suse.com/999582","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2014-3499","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-5277","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-6407","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-6408","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-8178","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-8179","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-9356","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-9357","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-9358","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-3627","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-3629","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-3630","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-3631","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-3697","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-8867","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-9962","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-14992","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-16539","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-10892","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-15664","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-16873","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-16874","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-16875","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-20699","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-13509","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-14271","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-12912","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-13401","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-15257","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-8694","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-8695","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-21284","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-21285","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41089","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41091","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41092","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41103","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41190","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-43565","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-24769","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-27191","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-36109","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-23650","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-23651","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-23652","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-23653","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-29018","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41110","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22868","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22869","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202503545-1/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2023-28840","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-28840","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-7474-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2023-28841","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-28842","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-23651","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-23652","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36621","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36623","tags":["report"]},{"url":"","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2022-41723","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2023-28840","title":"moby/moby's dockerd daemon encrypted overlay network may be unauthenticated","description":"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*.\n\nSwarm 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.\n\nThe 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.\n\nEncrypted 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.\n\nWhen 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.\n\nTwo iptables rules serve to filter incoming VXLAN datagrams with a VNI that corresponds to an encrypted network and discards unencrypted datagrams. The rules are appended to the end of the INPUT filter chain, following any rules that have been previously set by the system administrator. Administrator-set rules take precedence over the rules Moby sets to discard unencrypted VXLAN datagrams, which can potentially admit unencrypted datagrams that should have been discarded.\n\nThe injection of arbitrary Ethernet frames can enable a Denial of Service attack. A sophisticated attacker may be able to establish a UDP or TCP connection by way of the container’s outbound gateway that would otherwise be blocked by a stateful firewall, or carry out other escalations beyond simple injection by smuggling packets into the overlay network.\n\nPatches 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.\n\nSome workarounds are available. Close the VXLAN port (by default, UDP port 4789) to incoming traffic at the Internet boundary to prevent all VXLAN packet injection, and/or ensure that the `xt_u32` kernel module is available on all nodes of the Swarm cluster.","status":"published","published":"2023-04-04T21:13:03.347Z","modified":"2025-02-13T16:48:53.71Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:L","level":"high","assessor":"cna"}],"cwes":["CWE-420","CWE-636"],"updated_at":"2026-11-02T14:35:32.752775Z"}],"euvd":[{"id":"EUVD-2023-1150","description":"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*.\n\nSwarm 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.\n\nThe 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.\n\nEncrypted 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.\n\nWhen 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.\n\nTwo iptables rules serve to filter incoming VXLAN datagrams with a VNI that corresponds to an encrypted network and discards unencrypted datagrams. The rules are appended to the end of the INPUT filter chain, following any rules that have been previously set by the system administrator. Administrator-set rules take precedence over the rules Moby sets to discard unencrypted VXLAN datagrams, which can potentially admit unencrypted datagrams that should have been discarded.\n\nThe injection of arbitrary Ethernet frames can enable a Denial of Service attack. A sophisticated attacker may be able to establish a UDP or TCP connection by way of the container’s outbound gateway that would otherwise be blocked by a stateful firewall, or carry out other escalations beyond simple injection by smuggling packets into the overlay network.\n\nPatches 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.\n\nSome workarounds are available. Close the VXLAN port (by default, UDP port 4789) to incoming traffic at the Internet boundary to prevent all VXLAN packet injection, and/or ensure that the `xt_u32` kernel module is available on all nodes of the Swarm cluster.","status":"published","published":"2023-04-04T21:13:03Z","modified":"2025-02-13T16:48:53Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:L","level":"high"}],"updated_at":"2026-11-03T00:03:50.947767Z"}],"ghsa":[{"id":"GHSA-232p-vwff-86mp","title":"Docker Swarm encrypted overlay network may be unauthenticated","description":"[Moby](https://mobyproject.org/) 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](https://github.com/moby/moby) is commonly referred to as *Docker*.\n\nSwarm 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](https://github.com/moby/swarmkit) and supporting network code.\n\nThe `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](https://en.wikipedia.org/wiki/Virtual_Extensible_LAN), 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.\n\nEncrypted overlay networks function by encapsulating the VXLAN datagrams through the use of the [IPsec Encapsulating Security Payload](https://en.wikipedia.org/wiki/IPsec#Encapsulating_Security_Payload) protocol in [Transport mode](https://en.wikipedia.org/wiki/IPsec#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.\n\nWhen setting an endpoint up on an encrypted overlay network, Moby installs three [iptables](https://www.netfilter.org/projects/iptables/index.html) (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.\n\n[Two iptables rules](https://github.com/moby/libnetwork/blob/d9fae4c73daf76c3b0f77e14b45b8bf612ba764d/drivers/overlay/encryption.go#L230-L234) serve to filter incoming VXLAN datagrams with a VNI that corresponds to an encrypted network and discards unencrypted datagrams. The rules are appended to the end of the `INPUT` filter chain, following any rules that have been previously set by the system administrator. Administrator-set rules take precedence over the rules Moby sets to discard unencrypted VXLAN datagrams, which can potentially admit unencrypted datagrams that should have been discarded.\n\nOn Red Hat Enterprise Linux and derivatives such as CentOS and Rocky, the `xt_u32` module has been:\n* [moved to the kernel-modules-extra package and no longer installed by default in RHEL 8.3](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/8.3_release_notes/rhel-8-3-0-release#technology-preview_networking)\n* [officially deprecated in RHEL 8.6](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/8.6_release_notes/deprecated_functionality#deprecated-functionality_networking)\n* [removed completely in RHEL 9](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/considerations_in_adopting_rhel_9/assembly_networking_considerations-in-adopting-rhel-9#ref_firewall-networking_assembly_networking)\n\nThese rules are not created when `xt_u32` is unavailable, even though the container is still attached to the network.\n\n## Impact\nEncrypted overlay networks on affected configurations silently accept cleartext VXLAN datagrams that are tagged with the VNI of an encrypted overlay network. As a result, it is possible to inject arbitrary Ethernet frames into the encrypted overlay network by encapsulating them in VXLAN datagrams.\n\nThe injection of arbitrary Ethernet frames can enable a Denial of Service attack. A sophisticated attacker may be able to establish a UDP or TCP connection by way of the container’s outbound gateway that would otherwise be blocked by a stateful firewall, or carry out other escalations beyond simple injection by smuggling packets into the overlay network.\n\n## Patches\nPatches 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.\n\n## Workarounds\n* Close the VXLAN port (by default, UDP port 4789) to incoming traffic at the Internet boundary (see [GHSA-vwm3-crmr-xfxw](https://github.com/moby/moby/security/advisories/GHSA-vwm3-crmr-xfxw)) to prevent all VXLAN packet injection.\n* Ensure that the `xt_u32` kernel module is available on all nodes of the Swarm cluster.\n\n## Background\n* [#43382](https://github.com/moby/moby/issues/43382) partially discussed this concern, but did not consider the security implications.\n* Mirantis FIELD-5788 essentially duplicates [#43382](https://github.com/moby/moby/issues/43382), and was created six months earlier; it similarly overlooked the security implications.\n* [#45118](https://github.com/moby/moby/pull/45118) is the ancestor of the final patches, and was where the security implications were discovered.\n\n## Related\n* [CVE-2023-28841: Encrypted overlay network traffic may be unencrypted](https://github.com/moby/moby/security/advisories/GHSA-33pg-m6jh-5237)\n* [CVE-2023-28842: Encrypted overlay network with a single endpoint is unauthenticated](https://github.com/moby/moby/security/advisories/GHSA-6wrf-mxfj-pf5p)\n* [GHSA-vwm3-crmr-xfxw: The Swarm VXLAN port may be exposed to attack due to ambiguous documentation](https://github.com/moby/moby/security/advisories/GHSA-vwm3-crmr-xfxw)\n* [GHSA-gvm4-2qqg-m333: Security issues in encrypted overlay networks](https://github.com/moby/libnetwork/security/advisories/GHSA-gvm4-2qqg-m333) (libnetwork)","status":"published","published":"2023-04-04T21:13:06Z","modified":"2023-04-05T23:16:24Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:L","level":"high"}],"cwes":["CWE-420","CWE-636"],"updated_at":"2026-11-02T14:36:49.768564Z"}],"nvd":[{"id":"CVE-2023-28840","description":"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*.\n\nSwarm 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.\n\nThe 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.\n\nEncrypted 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.\n\nWhen 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.\n\nTwo iptables rules serve to filter incoming VXLAN datagrams with a VNI that corresponds to an encrypted network and discards unencrypted datagrams. The rules are appended to the end of the INPUT filter chain, following any rules that have been previously set by the system administrator. Administrator-set rules take precedence over the rules Moby sets to discard unencrypted VXLAN datagrams, which can potentially admit unencrypted datagrams that should have been discarded.\n\nThe injection of arbitrary Ethernet frames can enable a Denial of Service attack. A sophisticated attacker may be able to establish a UDP or TCP connection by way of the container’s outbound gateway that would otherwise be blocked by a stateful firewall, or carry out other escalations beyond simple injection by smuggling packets into the overlay network.\n\nPatches 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.\n\nSome workarounds are available. Close the VXLAN port (by default, UDP port 4789) to incoming traffic at the Internet boundary to prevent all VXLAN packet injection, and/or ensure that the `xt_u32` kernel module is available on all nodes of the Swarm cluster.","status":"published","published":"2023-04-04T22:15:07.853Z","modified":"2026-06-17T05:48:53.283Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:L","level":"high","assessor":"secondary"},{"version":"3.1","score":8.7,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H","level":"high","assessor":"primary"}],"cwes":["CWE-420","CWE-636","CWE-203","CWE-755"],"updated_at":"2026-11-02T14:07:53.719171Z"}],"osv":[{"id":"ALPINE-CVE-2023-28840","description":"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*.\n\nSwarm 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.\n\nThe 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.\n\nEncrypted 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.\n\nWhen 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.\n\nTwo iptables rules serve to filter incoming VXLAN datagrams with a VNI that corresponds to an encrypted network and discards unencrypted datagrams. The rules are appended to the end of the INPUT filter chain, following any rules that have been previously set by the system administrator. Administrator-set rules take precedence over the rules Moby sets to discard unencrypted VXLAN datagrams, which can potentially admit unencrypted datagrams that should have been discarded.\n\nThe injection of arbitrary Ethernet frames can enable a Denial of Service attack. A sophisticated attacker may be able to establish a UDP or TCP connection by way of the container’s outbound gateway that would otherwise be blocked by a stateful firewall, or carry out other escalations beyond simple injection by smuggling packets into the overlay network.\n\nPatches 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.\n\nSome workarounds are available. Close the VXLAN port (by default, UDP port 4789) to incoming traffic at the Internet boundary to prevent all VXLAN packet injection, and/or ensure that the `xt_u32` kernel module is available on all nodes of the Swarm cluster.","status":"published","published":"2023-04-04T22:15:07.853Z","modified":"2026-11-03T06:32:48.329237862Z","cvss":[{"version":"3.1","score":8.7,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H","level":"high"}],"updated_at":"2026-11-03T07:16:46.202932Z"},{"id":"BELL-CVE-2023-28840","title":"CVE-2023-28840 does not affect BellSoft software","status":"withdrawn","published":"2023-08-31T12:13:22.742164Z","modified":"2026-01-26T09:47:07.103085Z","cvss":[{"version":"3.1","score":8.7,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:28:17.742221Z"},{"id":"CVE-2023-28840","title":"moby/moby's dockerd daemon encrypted overlay network may be unauthenticated","description":"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*.\n\nSwarm 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.\n\nThe 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.\n\nEncrypted 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.\n\nWhen 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.\n\nTwo iptables rules serve to filter incoming VXLAN datagrams with a VNI that corresponds to an encrypted network and discards unencrypted datagrams. The rules are appended to the end of the INPUT filter chain, following any rules that have been previously set by the system administrator. Administrator-set rules take precedence over the rules Moby sets to discard unencrypted VXLAN datagrams, which can potentially admit unencrypted datagrams that should have been discarded.\n\nThe injection of arbitrary Ethernet frames can enable a Denial of Service attack. A sophisticated attacker may be able to establish a UDP or TCP connection by way of the container’s outbound gateway that would otherwise be blocked by a stateful firewall, or carry out other escalations beyond simple injection by smuggling packets into the overlay network.\n\nPatches 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.\n\nSome workarounds are available. Close the VXLAN port (by default, UDP port 4789) to incoming traffic at the Internet boundary to prevent all VXLAN packet injection, and/or ensure that the `xt_u32` kernel module is available on all nodes of the Swarm cluster.","status":"published","published":"2023-04-04T21:13:03.347Z","modified":"2026-10-28T02:30:48.187360872Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:L","level":"high"}],"cwes":["CWE-420","CWE-636"],"updated_at":"2026-11-02T15:44:31.468318Z"},{"id":"DEBIAN-CVE-2023-28840","description":"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.  Two iptables rules serve to filter incoming VXLAN datagrams with a VNI that corresponds to an encrypted network and discards unencrypted datagrams. The rules are appended to the end of the INPUT filter chain, following any rules that have been previously set by the system administrator. Administrator-set rules take precedence over the rules Moby sets to discard unencrypted VXLAN datagrams, which can potentially admit unencrypted datagrams that should have been discarded.  The injection of arbitrary Ethernet frames can enable a Denial of Service attack. A sophisticated attacker may be able to establish a UDP or TCP connection by way of the container’s outbound gateway that would otherwise be blocked by a stateful firewall, or carry out other escalations beyond simple injection by smuggling packets into the overlay network.  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.  Some workarounds are available. Close the VXLAN port (by default, UDP port 4789) to incoming traffic at the Internet boundary to prevent all VXLAN packet injection, and/or ensure that the `xt_u32` kernel module is available on all nodes of the Swarm cluster.","status":"published","published":"2023-04-04T22:15:07.853Z","modified":"2026-10-26T18:00:49.533000894Z","cvss":[{"version":"3.1","score":8.7,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:45:39.679062Z"},{"id":"GHSA-232p-vwff-86mp","title":"Docker Swarm encrypted overlay network may be unauthenticated","description":"[Moby](https://mobyproject.org/) 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](https://github.com/moby/moby) is commonly referred to as *Docker*.\n\nSwarm 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](https://github.com/moby/swarmkit) and supporting network code.\n\nThe `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](https://en.wikipedia.org/wiki/Virtual_Extensible_LAN), 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.\n\nEncrypted overlay networks function by encapsulating the VXLAN datagrams through the use of the [IPsec Encapsulating Security Payload](https://en.wikipedia.org/wiki/IPsec#Encapsulating_Security_Payload) protocol in [Transport mode](https://en.wikipedia.org/wiki/IPsec#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.\n\nWhen setting an endpoint up on an encrypted overlay network, Moby installs three [iptables](https://www.netfilter.org/projects/iptables/index.html) (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.\n\n[Two iptables rules](https://github.com/moby/libnetwork/blob/d9fae4c73daf76c3b0f77e14b45b8bf612ba764d/drivers/overlay/encryption.go#L230-L234) serve to filter incoming VXLAN datagrams with a VNI that corresponds to an encrypted network and discards unencrypted datagrams. The rules are appended to the end of the `INPUT` filter chain, following any rules that have been previously set by the system administrator. Administrator-set rules take precedence over the rules Moby sets to discard unencrypted VXLAN datagrams, which can potentially admit unencrypted datagrams that should have been discarded.\n\nOn Red Hat Enterprise Linux and derivatives such as CentOS and Rocky, the `xt_u32` module has been:\n* [moved to the kernel-modules-extra package and no longer installed by default in RHEL 8.3](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/8.3_release_notes/rhel-8-3-0-release#technology-preview_networking)\n* [officially deprecated in RHEL 8.6](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/8.6_release_notes/deprecated_functionality#deprecated-functionality_networking)\n* [removed completely in RHEL 9](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/considerations_in_adopting_rhel_9/assembly_networking_considerations-in-adopting-rhel-9#ref_firewall-networking_assembly_networking)\n\nThese rules are not created when `xt_u32` is unavailable, even though the container is still attached to the network.\n\n## Impact\nEncrypted overlay networks on affected configurations silently accept cleartext VXLAN datagrams that are tagged with the VNI of an encrypted overlay network. As a result, it is possible to inject arbitrary Ethernet frames into the encrypted overlay network by encapsulating them in VXLAN datagrams.\n\nThe injection of arbitrary Ethernet frames can enable a Denial of Service attack. A sophisticated attacker may be able to establish a UDP or TCP connection by way of the container’s outbound gateway that would otherwise be blocked by a stateful firewall, or carry out other escalations beyond simple injection by smuggling packets into the overlay network.\n\n## Patches\nPatches 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.\n\n## Workarounds\n* Close the VXLAN port (by default, UDP port 4789) to incoming traffic at the Internet boundary (see [GHSA-vwm3-crmr-xfxw](https://github.com/moby/moby/security/advisories/GHSA-vwm3-crmr-xfxw)) to prevent all VXLAN packet injection.\n* Ensure that the `xt_u32` kernel module is available on all nodes of the Swarm cluster.\n\n## Background\n* [#43382](https://github.com/moby/moby/issues/43382) partially discussed this concern, but did not consider the security implications.\n* Mirantis FIELD-5788 essentially duplicates [#43382](https://github.com/moby/moby/issues/43382), and was created six months earlier; it similarly overlooked the security implications.\n* [#45118](https://github.com/moby/moby/pull/45118) is the ancestor of the final patches, and was where the security implications were discovered.\n\n## Related\n* [CVE-2023-28841: Encrypted overlay network traffic may be unencrypted](https://github.com/moby/moby/security/advisories/GHSA-33pg-m6jh-5237)\n* [CVE-2023-28842: Encrypted overlay network with a single endpoint is unauthenticated](https://github.com/moby/moby/security/advisories/GHSA-6wrf-mxfj-pf5p)\n* [GHSA-vwm3-crmr-xfxw: The Swarm VXLAN port may be exposed to attack due to ambiguous documentation](https://github.com/moby/moby/security/advisories/GHSA-vwm3-crmr-xfxw)\n* [GHSA-gvm4-2qqg-m333: Security issues in encrypted overlay networks](https://github.com/moby/libnetwork/security/advisories/GHSA-gvm4-2qqg-m333) (libnetwork)","status":"published","published":"2023-04-04T21:13:06Z","modified":"2026-09-10T03:49:53.209500865Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:L","level":"high"}],"cwes":["CWE-420","CWE-636"],"updated_at":"2026-11-02T15:46:33.520522Z"},{"id":"OESA-2023-1238","title":"docker security update","description":"Docker is an open source project to build, ship and run any application as a lightweight container.\r\n\r\nSecurity Fix(es):\r\n\r\nMoby) 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 the VXLAN metadata, including 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\u0026apos;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. The `overlay` driver dynamically and lazily defines the kernel configuration for the VXLAN network on each node as containers are attached and detached. Routes and encryption parameters are only defined for destination nodes that participate in the network. The iptables rules that prevent encrypted overlay networks from accepting unencrypted packets are not created until a peer is available with which to communicate. Encrypted overlay networks silently accept cleartext VXLAN datagrams that are tagged with the VNI of an encrypted overlay network. As a result, it is possible to inject arbitrary Ethernet frames into the encrypted overlay network by encapsulating them in VXLAN datagrams. The implications of this can be quite dire, and GHSA-vwm3-crmr-xfxw should be referenced for a deeper exploration. Patches are available in Moby releases 23.0.3, and 20.10.24. As Mirantis Container Runtime\u0026apos;s 20.10 releases are numbered differently, users of that platform should update to 20.10.16. Some workarounds are available. In multi-node clusters, deploy a global ‘pause’ container for each encrypted overlay network, on every node. For a single-node cluster, do not use overlay networks of any sort. Bridge networks provide the same connectivity on a single node and have no multi-node features. The Swarm ingress feature is implemented using an overlay network, but can be disabled by publishing ports in `host` mode instead of `ingress` mode (allowing the use of an external load balancer), and removing the `ingress` network. If encrypted overlay networks are in exclusive use, block UDP port 4789 from traffic that has not been validated by IPSec.(CVE-2023-28842)\r\n\r\nMoby 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 the VXLAN metadata, including 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\u0026apos;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. 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 use Swarm encrypted overlay networks to provide confidentiality, which due to this vulnerability this is no longer guaranteed. Patches are available in Moby releases 23.0.3, and 20.10.24. As Mirantis Container Runtime\u0026apos;s 20.10 releases are numbered differently, users of that platform should update to 20.10.16. Some workarounds are available. Close the VXLAN port (by default, UDP port 4789) to outgoing traffic at the Internet boundary in order to prevent unintentionally leaking unencrypted traffic over the Internet, and/or ensure that the `xt_u32` kernel module is available on all nodes of the Swarm cluster.(CVE-2023-28841)\r\n\r\nMoby 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\u0026apos;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. Two iptables rules serve to filter incoming VXLAN datagrams with a VNI that corresponds to an encrypted network and discards unencrypted datagrams. The rules are appended to the end of the INPUT filter chain, following any rules that have been previously set by the system administrator. Administrator-set rules take precedence over the rules Moby sets to discard unencrypted VXLAN datagrams, which can potentially admit unencrypted datagrams that should have been discarded. The injection of arbitrary Ethernet frames can enable a Denial of Service attack. A sophisticated attacker may be able to establish a UDP or TCP connection by way of the container’s outbound gateway that would otherwise be blocked by a stateful firewall, or carry out other escalations beyond simple injection by smuggling packets into the overlay network. Patches are available in Moby releases 23.0.3 and 20.10.24. As Mirantis Container Runtime\u0026apos;s 20.10 releases are numbered differently, users of that platform should update to 20.10.16. Some workarounds are available. Close the VXLAN port (by default, UDP port 4789) to incoming traffic at the Internet boundary to prevent all VXLAN packet injection, and/or ensure that the `xt_u32` kernel module is available on all nodes of the Swarm cluster.(CVE-2023-28840)","status":"published","published":"2023-04-21T11:05:42Z","modified":"2026-08-18T01:17:41.384311177Z","cvss":[{"version":"3.1","score":8.7,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:39.934788Z"},{"id":"UBUNTU-CVE-2023-28840","description":"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. Two iptables rules serve to filter incoming VXLAN datagrams with a VNI that corresponds to an encrypted network and discards unencrypted datagrams. The rules are appended to the end of the INPUT filter chain, following any rules that have been previously set by the system administrator. Administrator-set rules take precedence over the rules Moby sets to discard unencrypted VXLAN datagrams, which can potentially admit unencrypted datagrams that should have been discarded. The injection of arbitrary Ethernet frames can enable a Denial of Service attack. A sophisticated attacker may be able to establish a UDP or TCP connection by way of the container’s outbound gateway that would otherwise be blocked by a stateful firewall, or carry out other escalations beyond simple injection by smuggling packets into the overlay network. 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. Some workarounds are available. Close the VXLAN port (by default, UDP port 4789) to incoming traffic at the Internet boundary to prevent all VXLAN packet injection, and/or ensure that the `xt_u32` kernel module is available on all nodes of the Swarm cluster.","status":"published","published":"2023-04-04T22:15:00Z","modified":"2026-05-20T16:13:33.091260159Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:L","level":"high"},{"version":"3.1","score":8.7,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T16:54:20.997471Z"},{"id":"GO-2023-1699","title":"Docker Swarm encrypted overlay network may be unauthenticated in github.com/docker/docker","description":"Docker Swarm encrypted overlay network may be unauthenticated in github.com/docker/docker","status":"published","published":"2024-08-20T20:29:17Z","modified":"2026-02-04T02:52:12.533309Z","updated_at":"2026-11-02T15:47:01.185262Z"},{"id":"MGASA-2023-0329","title":"Updated docker packages fix security vulnerabilities and bugs","description":"This update fixes several security issues and also solves some other\nissues\n\n- manage change of launch option earlier in post process\n- Automatically convert -g option to --data-root in installed\n  /etc/sysconfig/docker-storage\n- Fix CVE-2023-26054 and CVE-2023-2884[0-2]\n","status":"published","published":"2023-11-29T21:00:43Z","modified":"2026-04-16T04:44:45.759355973Z","updated_at":"2026-11-02T15:49:42.684501Z"},{"id":"openSUSE-SU-2024:12876-1","title":"docker-compose-2.17.3-1.1 on GA media","description":"These are all security issues fixed in the docker-compose-2.17.3-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-06-15T00:00:00Z","modified":"2026-02-04T03:50:07.833322Z","updated_at":"2026-11-02T16:58:36.025801Z"},{"id":"openSUSE-SU-2024:13005-1","title":"kubescape-2.3.6-1.1 on GA media","description":"These are all security issues fixed in the kubescape-2.3.6-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-06-15T00:00:00Z","modified":"2026-02-04T03:55:59.928742Z","updated_at":"2026-11-02T16:58:36.025801Z"},{"id":"openSUSE-SU-2024:13205-1","title":"docker-24.0.5_ce-2.1 on GA media","description":"These are all security issues fixed in the docker-24.0.5_ce-2.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-06-15T00:00:00Z","modified":"2026-02-04T03:22:09.089002Z","updated_at":"2026-11-02T16:58:36.025801Z"},{"id":"openSUSE-SU-2025:15589-1","title":"docker-stable-24.0.9_ce-15.1 on GA media","description":"These are all security issues fixed in the docker-stable-24.0.9_ce-15.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2025-09-30T00:00:00Z","modified":"2026-03-23T04:53:58.562077Z","updated_at":"2026-11-02T16:58:37.810934Z"},{"id":"SUSE-SU-2023:3307-1","title":"Security update for docker","description":"This update for docker fixes the following issues:\n\n- Update to v20.10.25-ce\n- CVE-2023-28840: Fixed a bug where an attacker could inject arbitrary Ethernet frames to execute a Denial of Service attack. (bsc#1214107)\n- CVE-2023-28841: Fixed a bug which allows an attacker to sit in a trusted position on the network and read all of the application traffic that is moving across the overlay network, resulting in unexpected secrets or user data disclosure (bsc#1214108)\n- CVE-2023-28842: Fixed a bug which allows an attacker to inject arbitrary Ethernet frames into the encrypted overlay network by encapsulating them in VXLAN datagrams. (bsc#1214109)\n","status":"published","published":"2023-08-14T08:52:14Z","modified":"2026-02-04T03:02:36.605765Z","updated_at":"2026-11-02T15:53:53.440387Z"},{"id":"SUSE-SU-2023:3536-1","title":"Security update for docker","description":"This update for docker fixes the following issues:\n\n- Update to Docker 24.0.5-ce.\n\n  See upstream changelong online at\n  \u003chttps://docs.docker.com/engine/release-notes/24.0/#2405\u003e bsc#1213229 \n\n- Update to Docker 24.0.4-ce.\n\n  See upstream changelog online at\n  \u003chttps://docs.docker.com/engine/release-notes/24.0/#2404\u003e. bsc#1213500\n\n- Update to Docker 24.0.3-ce.\n\n  See upstream changelog online at\n  \u003chttps://docs.docker.com/engine/release-notes/24.0/#2403\u003e. bsc#1213120\n\n- Recommend docker-rootless-extras instead of Require(ing) it, given\n  it's an additional functionality and not inherently required for\n  docker to function.\n\n- Add docker-rootless-extras subpackage (https://docs.docker.com/engine/security/rootless)\n\n- Update to Docker 24.0.2-ce. See upstream changelog online at\n  \u003chttps://docs.docker.com/engine/release-notes/24.0/#2402\u003e. bsc#1212368\n\n  * Includes the upstreamed fix for the mount table pollution issue.\n    bsc#1210797\n\n- Add Recommends for docker-buildx, and add /usr/lib/docker/cli-plugins as\n  being provided by this package.\n\n- was rebuilt against current GO compiler.\n\n","status":"published","published":"2023-09-05T13:01:38Z","modified":"2026-02-04T02:51:28.334747Z","updated_at":"2026-11-02T15:53:53.440387Z"},{"id":"SUSE-SU-2025:03540-1","title":"Security update for docker-stable","description":"This update for docker-stable fixes the following issues:\n\n- Include historical changelog data from before the docker-stable fork. The\n  initial changelog entry did technically provide all the necessary\n  information, but our CVE tracking tools do not understand how the package is\n  forked and so it seems that this package does not include fixes for ~12 years\n  of updates. So, include a copy of the original package's changelog up until\n  the fork point. (bsc#1250596)\n\n- Remove git-core recommends on SLE. Most SLE systems have\n  installRecommends=yes by default and thus end up installing git with Docker.\n  bsc#1250508\n\n  This feature is mostly intended for developers ('docker build git://') so\n  most users already have the dependency installed, and the error when git is\n  missing is fairly straightforward (so they can easily figure out what they\n  need to install).\n\n- Backport \u003chttps://github.com/moby/moby/pull/48517\u003e. bsc#1247362\n\n- Update to docker-buildx v0.25.0. Upstream changelog:\n  \u003chttps://github.com/docker/buildx/releases/tag/v0.25.0\u003e\n\n- Do not try to inject SUSEConnect secrets when in Rootless Docker mode, as\n  Docker does not have permission to access the host zypper credentials in this\n  mode (and unprivileged users cannot disable the feature using\n  /etc/docker/suse-secrets-enable.) bsc#1240150\n\n- Initial docker-stable fork, forked from Docker 24.0.7-ce release\n  (packaged on 2024-02-14). The original changelog is included below for\n  historical reference.\n","status":"published","published":"2025-10-10T19:04:02Z","modified":"2026-02-04T02:38:37.010407Z","updated_at":"2026-11-02T15:53:58.883365Z"},{"id":"SUSE-SU-2025:03545-1","title":"Security update for docker-stable","description":"This update for docker-stable fixes the following issues:\n\nNote this update contains a already fixed references mostly.\n\n- Remove git-core recommends on SLE to avoid pulling it in unnecessary. (bsc#1250508)\n\n  This feature is mostly intended for developers ('docker build git://') so\n  most users already have the dependency installed, and the error when git is\n  missing is fairly straightforward (so they can easily figure out what they\n  need to install).\n\n- Include historical changelog data from before the docker-stable fork. The\n  initial changelog entry did technically provide all the necessary\n  information, but our CVE tracking tools do not understand how the package is\n  forked and so it seems that this package does not include fixes for ~12 years\n  of updates. So, include a copy of the original package's changelog up until\n  the fork point. bsc#1250596\n\n- Update to docker-buildx v0.25.0. Upstream changelog:\n  \u003chttps://github.com/docker/buildx/releases/tag/v0.25.0\u003e\n\n- Update to Go 1.23 for building now that upstream has switched their 23.0.x\n  LTSS to use Go 1.23.\n\n- Do not try to inject SUSEConnect secrets when in Rootless Docker mode, as\n  Docker does not have permission to access the host zypper credentials in this\n  mode (and unprivileged users cannot disable the feature using\n  /etc/docker/suse-secrets-enable.) bsc#1240150\n\n- Initial docker-stable fork, forked from Docker 24.0.7-ce release\n  (packaged on 2024-02-14). The original changelog is included below for\n  historical reference.\n","status":"published","published":"2025-10-11T01:20:50Z","modified":"2026-03-23T04:48:05.17767Z","updated_at":"2026-11-02T15:53:58.883365Z"},{"id":"USN-7474-1","title":"docker.io vulnerabilities","description":"Cory Snider discovered that Docker incorrectly handled networking packet\nencapsulation. An attacker could use this issue to inject internet\npackets in established connection, possibly causing a denial of service or\nbypassing firewall protections. This issue only affected Ubuntu 22.04 LTS,\nUbuntu 20.04 LTS, and Ubuntu 18.04 LTS. (CVE-2023-28840, CVE-2023-28841,\nCVE-2023-28842)\n\nRory McNamara discovered that Docker incorrectly handled cache in the\nBuildKit toolkit. An attacker could possibly use this issue to expose\nsensitive information. (CVE-2024-23651)\n\nIt was discovered that Docker incorrectly handled parallel operations in\nsome circumstances, which could possibly lead to undefined behavior.\n(CVE-2024-36621, CVE-2024-36623)\n\nRory McNamara discovered that Docker incorrectly verified file paths during\na certain command in the BuildKit toolkit. An attacker could possibly use\nthis issue to delete arbitrary files from the system. (CVE-2024-23652)\n","status":"published","published":"2025-05-01T13:54:03Z","modified":"2026-04-27T17:57:08.511503Z","updated_at":"2026-11-02T16:58:19.988474Z"}]}}