Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

moby/moby's dockerd daemon encrypted overlay network traffic may be unencrypted

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2023-28841

Published

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

Source published
4 Apr 2023 21:12:17 UTC
Source modified
13 Feb 2025 16:48:54 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · 6.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N

euvd · EUVD-2023-1167

Published

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

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Apr 4, 2023, 9:12:17 PM

dateUpdated: Feb 13, 2025, 4:48:54 PM

10 related source bulletins · separate from aliases

WID-SEC-W-2023-1183: docker: Mehrere Schwachstellen

CVE-2023-24532 · CVE-2023-25809 · CVE-2023-27561 · CVE-2023-28642 · CVE-2023-28840 · CVE-2023-28841 · CVE-2023-28842

SUSE-SU-2025:03540-1: Security update for docker-stable

CVE-2014-3499 · CVE-2014-5277 · CVE-2014-6407 · CVE-2014-6408 · CVE-2014-8178 · CVE-2014-8179 · CVE-2014-9356 · CVE-2014-9357 · CVE-2014-9358 · CVE-2015-3627 · CVE-2015-3629 · CVE-2015-3630 · CVE-2015-3631 · CVE-2016-3697 · CVE-2016-8867 · CVE-2016-9962 · CVE-2017-14992 · CVE-2017-16539 · CVE-2018-10892 · CVE-2018-15664 · CVE-2018-16873 · CVE-2018-16874 · CVE-2018-16875 · CVE-2018-20699 · CVE-2019-13509 · CVE-2019-14271 · CVE-2020-12912 · CVE-2020-13401 · CVE-2020-15257 · CVE-2020-8694 · CVE-2020-8695 · CVE-2021-21284 · CVE-2021-21285 · CVE-2021-41089 · CVE-2021-41091 · CVE-2021-41092 · CVE-2021-41103 · CVE-2021-41190 · CVE-2021-43565 · CVE-2022-24769 · CVE-2022-27191 · CVE-2022-36109 · CVE-2023-28840 · CVE-2023-28841 · CVE-2023-28842 · CVE-2024-23650 · CVE-2024-23651 · CVE-2024-23652 · CVE-2024-23653 · CVE-2024-29018 · CVE-2024-41110 · CVE-2025-22868 · CVE-2025-22869

SUSE-SU-2023:3307-1: Security update for docker

CVE-2023-28840 · CVE-2023-28841 · CVE-2023-28842

SUSE-SU-2023:3536-1: Security update for docker

CVE-2023-28840 · CVE-2023-28841 · CVE-2023-28842

openSUSE-SU-2024:13205-1: docker-24.0.5_ce-2.1 on GA media

CVE-2023-28840 · CVE-2023-28841 · CVE-2023-28842

SUSE-SU-2025:03545-1: Security update for docker-stable

CVE-2014-3499 · CVE-2014-5277 · CVE-2014-6407 · CVE-2014-6408 · CVE-2014-8178 · CVE-2014-8179 · CVE-2014-9356 · CVE-2014-9357 · CVE-2014-9358 · CVE-2015-3627 · CVE-2015-3629 · CVE-2015-3630 · CVE-2015-3631 · CVE-2016-3697 · CVE-2016-8867 · CVE-2016-9962 · CVE-2017-14992 · CVE-2017-16539 · CVE-2018-10892 · CVE-2018-15664 · CVE-2018-16873 · CVE-2018-16874 · CVE-2018-16875 · CVE-2018-20699 · CVE-2019-13509 · CVE-2019-14271 · CVE-2020-12912 · CVE-2020-13401 · CVE-2020-15257 · CVE-2020-8694 · CVE-2020-8695 · CVE-2021-21284 · CVE-2021-21285 · CVE-2021-41089 · CVE-2021-41091 · CVE-2021-41092 · CVE-2021-41103 · CVE-2021-41190 · CVE-2021-43565 · CVE-2022-24769 · CVE-2022-27191 · CVE-2022-36109 · CVE-2023-28840 · CVE-2023-28841 · CVE-2023-28842 · CVE-2024-23650 · CVE-2024-23651 · CVE-2024-23652 · CVE-2024-23653 · CVE-2024-29018 · CVE-2024-41110 · CVE-2025-22868 · CVE-2025-22869

openSUSE-SU-2025:15589-1: docker-stable-24.0.9_ce-15.1 on GA media

CVE-2014-3499 · CVE-2014-5277 · CVE-2014-6407 · CVE-2014-6408 · CVE-2014-8178 · CVE-2014-8179 · CVE-2014-9356 · CVE-2014-9357 · CVE-2014-9358 · CVE-2015-3627 · CVE-2015-3629 · CVE-2015-3630 · CVE-2015-3631 · CVE-2016-3697 · CVE-2016-8867 · CVE-2016-9962 · CVE-2017-14992 · CVE-2017-16539 · CVE-2018-10892 · CVE-2018-15664 · CVE-2018-16873 · CVE-2018-16874 · CVE-2018-16875 · CVE-2018-20699 · CVE-2019-13509 · CVE-2019-14271 · CVE-2020-12912 · CVE-2020-13401 · CVE-2020-15257 · CVE-2020-8694 · CVE-2020-8695 · CVE-2021-21284 · CVE-2021-41089 · CVE-2021-41092 · CVE-2021-41190 · CVE-2021-43565 · CVE-2022-24769 · CVE-2022-36109 · CVE-2023-28840 · CVE-2023-28841 · CVE-2023-28842 · CVE-2024-23651 · CVE-2024-23652

WID-SEC-W-2024-1591: Juniper JUNOS: Mehrere Schwachstellen

CVE-2006-20001 · CVE-2007-5846 · CVE-2008-6123 · CVE-2011-1473 · CVE-2011-5094 · CVE-2012-6151 · CVE-2014-10064 · CVE-2014-2285 · CVE-2014-2310 · CVE-2014-3565 · CVE-2014-7191 · CVE-2014-8882 · CVE-2015-5621 · CVE-2015-8100 · CVE-2015-9262 · CVE-2016-1000232 · CVE-2016-10540 · CVE-2016-4658 · CVE-2017-1000048 · CVE-2017-15010 · CVE-2018-18065 · CVE-2018-20834 · CVE-2018-3737 · CVE-2018-7408 · CVE-2019-10081 · CVE-2019-10082 · CVE-2019-10092 · CVE-2019-10097 · CVE-2019-10098 · CVE-2019-11719 · CVE-2019-11727 · CVE-2019-11756 · CVE-2019-16775 · CVE-2019-16776 · CVE-2019-16777 · CVE-2019-17006 · CVE-2019-17023 · CVE-2019-17567 · CVE-2019-20149 · CVE-2019-20892 · CVE-2019-9517 · CVE-2020-11668 · CVE-2020-11984 · CVE-2020-11993 · CVE-2020-12362 · CVE-2020-12400 · CVE-2020-12401 · CVE-2020-12402 · CVE-2020-12403 · CVE-2020-13938 · CVE-2020-13950 · CVE-2020-14145 · CVE-2020-15861 · CVE-2020-15862 · CVE-2020-1927 · CVE-2020-1934 · CVE-2020-28469 · CVE-2020-28502 · CVE-2020-35452 · CVE-2020-36049 · CVE-2020-6829 · CVE-2020-7660 · CVE-2020-7754 · CVE-2020-7774 · CVE-2020-8648 · CVE-2020-9490 · CVE-2021-22543 · CVE-2021-2342 · CVE-2021-23440 · CVE-2021-2356 · CVE-2021-2372 · CVE-2021-2385 · CVE-2021-2389 · CVE-2021-2390 · CVE-2021-25745 · CVE-2021-25746 · CVE-2021-25748 · CVE-2021-26690 · CVE-2021-26691 · CVE-2021-27290 · CVE-2021-29469 · CVE-2021-30641 · CVE-2021-31535 · CVE-2021-31618 · CVE-2021-3177 · CVE-2021-32803 · CVE-2021-32804 · CVE-2021-33033 · CVE-2021-33034 · CVE-2021-33193 · CVE-2021-3347 · CVE-2021-33909 · CVE-2021-34798 · CVE-2021-35604 · CVE-2021-35624 · CVE-2021-36160 · CVE-2021-37701 · CVE-2021-37712 · CVE-2021-37713 · CVE-2021-3803 · CVE-2021-39275 · CVE-2021-40438 · CVE-2021-41524 · CVE-2021-41773 · CVE-2021-42013 · CVE-2021-43527 · CVE-2021-44224 · CVE-2021-44225 · CVE-2021-44790 · CVE-2021-44906 · CVE-2022-21245 · CVE-2022-21270 · CVE-2022-21303 · CVE-2022-21304 · CVE-2022-21344 · CVE-2022-21367 · CVE-2022-21417 · CVE-2022-21427 · CVE-2022-21444 · CVE-2022-21451 · CVE-2022-21454 · CVE-2022-21460 · CVE-2022-21589 · CVE-2022-21592 · CVE-2022-21595 · CVE-2022-21608 · CVE-2022-21617 · CVE-2022-22719 · CVE-2022-22720 · CVE-2022-22721 · CVE-2022-22822 · CVE-2022-22823 · CVE-2022-22824 · CVE-2022-23471 · CVE-2022-23524 · CVE-2022-23525 · CVE-2022-23526 · CVE-2022-23852 · CVE-2022-23943 · CVE-2022-25147 · CVE-2022-25235 · CVE-2022-25236 · CVE-2022-2526 · CVE-2022-25315 · CVE-2022-26377 · CVE-2022-28330 · CVE-2022-28614 · CVE-2022-28615 · CVE-2022-29167 · CVE-2022-29404 · CVE-2022-30522 · CVE-2022-30556 · CVE-2022-31813 · CVE-2022-3517 · CVE-2022-3564 · CVE-2022-36760 · CVE-2022-37434 · CVE-2022-37436 · CVE-2022-40674 · CVE-2022-41741 · CVE-2022-41742 · CVE-2022-4203 · CVE-2022-4304 · CVE-2022-4450 · CVE-2022-46663 · CVE-2022-4886 · CVE-2023-0215 · CVE-2023-0216 · CVE-2023-0217 · CVE-2023-0286 · CVE-2023-0401 · CVE-2023-0464 · CVE-2023-0465 · CVE-2023-0466 · CVE-2023-0767 · CVE-2023-1255 · CVE-2023-2002 · CVE-2023-20593 · CVE-2023-21830 · CVE-2023-21840 · CVE-2023-21843 · CVE-2023-21912 · CVE-2023-21963 · CVE-2023-21980 · CVE-2023-22025 · CVE-2023-22067 · CVE-2023-22081 · CVE-2023-22652 · CVE-2023-24329 · CVE-2023-25153 · CVE-2023-25173 · CVE-2023-25690 · CVE-2023-2700 · CVE-2023-27522 · CVE-2023-2828 · CVE-2023-28840 · CVE-2023-28841 · CVE-2023-28842 · CVE-2023-2975 · CVE-2023-30079 · CVE-2023-30630 · CVE-2023-3090 · CVE-2023-32067 · CVE-2023-32360 · CVE-2023-32435 · CVE-2023-32439 · CVE-2023-32732 · CVE-2023-3341 · CVE-2023-3390 · CVE-2023-33953 · CVE-2023-34058 · CVE-2023-34059 · CVE-2023-3446 · CVE-2023-34969 · CVE-2023-35001 · CVE-2023-35788 · CVE-2023-3611 · CVE-2023-37450 · CVE-2023-3776 · CVE-2023-3817 · CVE-2023-4004 · CVE-2023-4206 · CVE-2023-4207 · CVE-2023-4208 · CVE-2023-42753 · CVE-2023-4785 · CVE-2023-4807 · CVE-2023-4863 · CVE-2023-5043 · CVE-2023-5129 · CVE-2023-5363 · CVE-2024-20918 · CVE-2024-20919 · CVE-2024-20921 · CVE-2024-20926 · CVE-2024-20932 · CVE-2024-20945 · CVE-2024-20952 · CVE-2024-39511 · CVE-2024-39512 · CVE-2024-39513 · CVE-2024-39514 · CVE-2024-39517 · CVE-2024-39518 · CVE-2024-39519 · CVE-2024-39520 · CVE-2024-39521 · CVE-2024-39522 · CVE-2024-39523 · CVE-2024-39524 · CVE-2024-39528 · CVE-2024-39529 · CVE-2024-39530 · CVE-2024-39531 · CVE-2024-39532 · CVE-2024-39533 · CVE-2024-39535 · CVE-2024-39536 · CVE-2024-39537 · CVE-2024-39538 · CVE-2024-39539 · CVE-2024-39540 · CVE-2024-39541 · CVE-2024-39542 · CVE-2024-39543 · CVE-2024-39545 · CVE-2024-39546 · CVE-2024-39548 · CVE-2024-39549 · CVE-2024-39550 · CVE-2024-39551 · CVE-2024-39553 · CVE-2024-39554 · CVE-2024-39555 · CVE-2024-39556 · CVE-2024-39557 · CVE-2024-39558 · CVE-2024-39559 · CVE-2024-39560 · CVE-2024-39561 · CVE-2024-39565

RHBA-2024:1246: Red Hat Bug Fix Advisory: Multicluster Engine for Kubernetes 2.4.4 bug fixes

CVE-2023-28840 · CVE-2023-28841 · CVE-2023-28842

WID-SEC-W-2024-0794: Dell ECS: Mehrere Schwachstellen

CVE-2018-18074 · CVE-2020-10663 · CVE-2020-10672 · CVE-2020-10673 · CVE-2020-10735 · CVE-2020-10968 · CVE-2020-10969 · CVE-2020-11111 · CVE-2020-11112 · CVE-2020-11113 · CVE-2020-11612 · CVE-2020-11619 · CVE-2020-11620 · CVE-2020-11979 · CVE-2020-12762 · CVE-2020-12825 · CVE-2020-13956 · CVE-2020-14060 · CVE-2020-14061 · CVE-2020-14062 · CVE-2020-14195 · CVE-2020-15250 · CVE-2020-1945 · CVE-2020-1967 · CVE-2020-1971 · CVE-2020-24616 · CVE-2020-24750 · CVE-2020-25649 · CVE-2020-25658 · CVE-2020-26116 · CVE-2020-26137 · CVE-2020-26541 · CVE-2020-27216 · CVE-2020-27218 · CVE-2020-27223 · CVE-2020-28366 · CVE-2020-28493 · CVE-2020-29509 · CVE-2020-29511 · CVE-2020-29582 · CVE-2020-29651 · CVE-2020-35490 · CVE-2020-35491 · CVE-2020-35728 · CVE-2020-36179 · CVE-2020-36180 · CVE-2020-36181 · CVE-2020-36182 · CVE-2020-36183 · CVE-2020-36184 · CVE-2020-36185 · CVE-2020-36186 · CVE-2020-36187 · CVE-2020-36188 · CVE-2020-36189 · CVE-2020-36516 · CVE-2020-36518 · CVE-2020-36557 · CVE-2020-36558 · CVE-2020-36691 · CVE-2020-7238 · CVE-2020-8840 · CVE-2020-8908 · CVE-2020-8911 · CVE-2020-8912 · CVE-2020-9488 · CVE-2020-9493 · CVE-2020-9546 · CVE-2020-9547 · CVE-2020-9548 · CVE-2021-20190 · CVE-2021-20323 · CVE-2021-21290 · CVE-2021-21295 · CVE-2021-21409 · CVE-2021-23840 · CVE-2021-23841 · CVE-2021-2471 · CVE-2021-25642 · CVE-2021-26341 · CVE-2021-27918 · CVE-2021-28153 · CVE-2021-28165 · CVE-2021-28169 · CVE-2021-28861 · CVE-2021-29425 · CVE-2021-30560 · CVE-2021-3114 · CVE-2021-33036 · CVE-2021-33194 · CVE-2021-33195 · CVE-2021-33196 · CVE-2021-33197 · CVE-2021-33503 · CVE-2021-33655 · CVE-2021-33656 · CVE-2021-3424 · CVE-2021-34428 · CVE-2021-3449 · CVE-2021-3450 · CVE-2021-3530 · CVE-2021-36221 · CVE-2021-36373 · CVE-2021-36374 · CVE-2021-3648 · CVE-2021-36690 · CVE-2021-3711 · CVE-2021-3712 · CVE-2021-37136 · CVE-2021-37137 · CVE-2021-37404 · CVE-2021-37533 · CVE-2021-3754 · CVE-2021-3778 · CVE-2021-3796 · CVE-2021-3826 · CVE-2021-3827 · CVE-2021-38297 · CVE-2021-3872 · CVE-2021-3875 · CVE-2021-3903 · CVE-2021-3923 · CVE-2021-3927 · CVE-2021-3928 · CVE-2021-3968 · CVE-2021-3973 · CVE-2021-3974 · CVE-2021-3984 · CVE-2021-4019 · CVE-2021-4037 · CVE-2021-4069 · CVE-2021-4104 · CVE-2021-4136 · CVE-2021-4157 · CVE-2021-4166 · CVE-2021-41771 · CVE-2021-4192 · CVE-2021-4193 · CVE-2021-4203 · CVE-2021-42567 · CVE-2021-43797 · CVE-2021-44531 · CVE-2021-44532 · CVE-2021-44533 · CVE-2021-44716 · CVE-2021-44878 · CVE-2021-45078 · CVE-2021-46195 · CVE-2021-46828 · CVE-2021-46848 · CVE-2022-0128 · CVE-2022-0213 · CVE-2022-0225 · CVE-2022-0261 · CVE-2022-0318 · CVE-2022-0319 · CVE-2022-0351 · CVE-2022-0359 · CVE-2022-0361 · CVE-2022-0392 · CVE-2022-0407 · CVE-2022-0413 · CVE-2022-0561 · CVE-2022-0696 · CVE-2022-0778 · CVE-2022-1184 · CVE-2022-1245 · CVE-2022-1271 · CVE-2022-1292 · CVE-2022-1381 · CVE-2022-1420 · CVE-2022-1462 · CVE-2022-1466 · CVE-2022-1471 · CVE-2022-1586 · CVE-2022-1587 · CVE-2022-1616 · CVE-2022-1619 · CVE-2022-1620 · CVE-2022-1679 · CVE-2022-1705 · CVE-2022-1720 · CVE-2022-1729 · CVE-2022-1733 · CVE-2022-1735 · CVE-2022-1771 · CVE-2022-1785 · CVE-2022-1796 · CVE-2022-1851 · CVE-2022-1897 · CVE-2022-1898 · CVE-2022-1927 · CVE-2022-1962 · CVE-2022-1968 · CVE-2022-1974 · CVE-2022-1975 · CVE-2022-20132 · CVE-2022-20141 · CVE-2022-20154 · CVE-2022-20166 · CVE-2022-20368 · CVE-2022-20369 · CVE-2022-2047 · CVE-2022-2048 · CVE-2022-20567 · CVE-2022-2068 · CVE-2022-2097 · CVE-2022-21216 · CVE-2022-21233 · CVE-2022-2124 · CVE-2022-2125 · CVE-2022-2126 · CVE-2022-2129 · CVE-2022-21363 · CVE-2022-21385 · CVE-2022-21499 · CVE-2022-2153 · CVE-2022-21540 · CVE-2022-21541 · CVE-2022-21549 · CVE-2022-21618 · CVE-2022-21619 · CVE-2022-21624 · CVE-2022-21626 · CVE-2022-21628 · CVE-2022-21702 · CVE-2022-2175 · CVE-2022-2182 · CVE-2022-2183 · CVE-2022-2206 · CVE-2022-2207 · CVE-2022-2208 · CVE-2022-2210 · CVE-2022-2231 · CVE-2022-2256 · CVE-2022-2257 · CVE-2022-2264 · CVE-2022-2284 · CVE-2022-2285 · CVE-2022-2286 · CVE-2022-2287 · CVE-2022-22976 · CVE-2022-22978 · CVE-2022-2304 · CVE-2022-2318 · CVE-2022-23302 · CVE-2022-23305 · CVE-2022-23307 · CVE-2022-2343 · CVE-2022-2344 · CVE-2022-2345 · CVE-2022-23471 · CVE-2022-23521 · CVE-2022-23772 · CVE-2022-23773 · CVE-2022-24302 · CVE-2022-24329 · CVE-2022-24823 · CVE-2022-24903 · CVE-2022-2503 · CVE-2022-25147 · CVE-2022-25168 · CVE-2022-2519 · CVE-2022-2520 · CVE-2022-2521 · CVE-2022-2522 · CVE-2022-25647 · CVE-2022-2571 · CVE-2022-2580 · CVE-2022-2581 · CVE-2022-25857 · CVE-2022-2588 · CVE-2022-2598 · CVE-2022-26148 · CVE-2022-26365 · CVE-2022-26373 · CVE-2022-2639 · CVE-2022-26612 · CVE-2022-2663 · CVE-2022-27781 · CVE-2022-27782 · CVE-2022-27943 · CVE-2022-2795 · CVE-2022-28131 · CVE-2022-2816 · CVE-2022-2817 · CVE-2022-2819 · CVE-2022-28327 · CVE-2022-2845 · CVE-2022-2849 · CVE-2022-2862 · CVE-2022-2867 · CVE-2022-2868 · CVE-2022-2869 · CVE-2022-28693 · CVE-2022-2874 · CVE-2022-28748 · CVE-2022-2880 · CVE-2022-2889 · CVE-2022-29162 · CVE-2022-29187 · CVE-2022-2923 · CVE-2022-2946 · CVE-2022-29526 · CVE-2022-29583 · CVE-2022-2964 · CVE-2022-2977 · CVE-2022-2980 · CVE-2022-2982 · CVE-2022-29900 · CVE-2022-29901 · CVE-2022-2991 · CVE-2022-3016 · CVE-2022-3028 · CVE-2022-3037 · CVE-2022-30580 · CVE-2022-30630 · CVE-2022-30631 · CVE-2022-30632 · CVE-2022-30633 · CVE-2022-3099 · CVE-2022-31030 · CVE-2022-31159 · CVE-2022-3134 · CVE-2022-3153 · CVE-2022-3169 · CVE-2022-31690 · CVE-2022-32148 · CVE-2022-32149 · CVE-2022-32206 · CVE-2022-32208 · CVE-2022-32221 · CVE-2022-3234 · CVE-2022-3235 · CVE-2022-3239 · CVE-2022-3278 · CVE-2022-3296 · CVE-2022-3297 · CVE-2022-33196 · CVE-2022-3324 · CVE-2022-3352 · CVE-2022-33740 · CVE-2022-33741 · CVE-2022-33742 · CVE-2022-33972 · CVE-2022-33981 · CVE-2022-34169 · CVE-2022-3424 · CVE-2022-34266 · CVE-2022-34526 · CVE-2022-34903 · CVE-2022-3491 · CVE-2022-3515 · CVE-2022-3520 · CVE-2022-3521 · CVE-2022-3524 · CVE-2022-35252 · CVE-2022-3542 · CVE-2022-3545 · CVE-2022-3564 · CVE-2022-3565 · CVE-2022-3566 · CVE-2022-3567 · CVE-2022-35737 · CVE-2022-3586 · CVE-2022-3591 · CVE-2022-3594 · CVE-2022-3597 · CVE-2022-3599 · CVE-2022-36109 · CVE-2022-3621 · CVE-2022-3626 · CVE-2022-3627 · CVE-2022-3628 · CVE-2022-36280 · CVE-2022-3629 · CVE-2022-3635 · CVE-2022-3643 · CVE-2022-36437 · CVE-2022-3646 · CVE-2022-3649 · CVE-2022-36760 · CVE-2022-36879 · CVE-2022-36946 · CVE-2022-3705 · CVE-2022-37434 · CVE-2022-37436 · CVE-2022-37865 · CVE-2022-37866 · CVE-2022-38090 · CVE-2022-38096 · CVE-2022-38126 · CVE-2022-38127 · CVE-2022-38177 · CVE-2022-38178 · CVE-2022-3821 · CVE-2022-38533 · CVE-2022-38749 · CVE-2022-38750 · CVE-2022-38751 · CVE-2022-38752 · CVE-2022-39028 · CVE-2022-3903 · CVE-2022-39188 · CVE-2022-39399 · CVE-2022-3970 · CVE-2022-40149 · CVE-2022-40150 · CVE-2022-40151 · CVE-2022-40152 · CVE-2022-40153 · CVE-2022-40303 · CVE-2022-40304 · CVE-2022-40307 · CVE-2022-40674 · CVE-2022-40768 · CVE-2022-40899 · CVE-2022-4095 · CVE-2022-41218 · CVE-2022-4129 · CVE-2022-4141 · CVE-2022-41717 · CVE-2022-41721 · CVE-2022-41848 · CVE-2022-41850 · CVE-2022-41854 · CVE-2022-41858 · CVE-2022-41881 · CVE-2022-41903 · CVE-2022-41915 · CVE-2022-41966 · CVE-2022-41974 · CVE-2022-42003 · CVE-2022-42004 · CVE-2022-42010 · CVE-2022-42011 · CVE-2022-42012 · CVE-2022-42328 · CVE-2022-42329 · CVE-2022-42703 · CVE-2022-42889 · CVE-2022-42895 · CVE-2022-42896 · CVE-2022-42898 · CVE-2022-4292 · CVE-2022-4293 · CVE-2022-42969 · CVE-2022-4304 · CVE-2022-43552 · CVE-2022-43680 · CVE-2022-43750 · CVE-2022-4378 · CVE-2022-43945 · CVE-2022-43995 · CVE-2022-4415 · CVE-2022-4450 · CVE-2022-44638 · CVE-2022-45061 · CVE-2022-45688 · CVE-2022-45884 · CVE-2022-45885 · CVE-2022-45886 · CVE-2022-45887 · CVE-2022-45919 · CVE-2022-45934 · CVE-2022-45939 · CVE-2022-4662 · CVE-2022-46751 · CVE-2022-46908 · CVE-2022-47629 · CVE-2022-47929 · CVE-2022-48281 · CVE-2022-48337 · CVE-2022-48339 · CVE-2023-0045 · CVE-2023-0049 · CVE-2023-0051 · CVE-2023-0054 · CVE-2023-0215 · CVE-2023-0286 · CVE-2023-0288 · CVE-2023-0433 · CVE-2023-0464 · CVE-2023-0465 · CVE-2023-0466 · CVE-2023-0512 · CVE-2023-0590 · CVE-2023-0597 · CVE-2023-0833 · CVE-2023-1076 · CVE-2023-1095 · CVE-2023-1118 · CVE-2023-1127 · CVE-2023-1170 · CVE-2023-1175 · CVE-2023-1370 · CVE-2023-1380 · CVE-2023-1390 · CVE-2023-1436 · CVE-2023-1513 · CVE-2023-1611 · CVE-2023-1670 · CVE-2023-1855 · CVE-2023-1989 · CVE-2023-1990 · CVE-2023-1998 · CVE-2023-20862 · CVE-2023-2124 · CVE-2023-2162 · CVE-2023-2176 · CVE-2023-21830 · CVE-2023-21835 · CVE-2023-21843 · CVE-2023-21930 · CVE-2023-21937 · CVE-2023-21938 · CVE-2023-21939 · CVE-2023-2194 · CVE-2023-21954 · CVE-2023-21967 · CVE-2023-21968 · CVE-2023-22490 · CVE-2023-2253 · CVE-2023-22809 · CVE-2023-23454 · CVE-2023-23455 · CVE-2023-23559 · CVE-2023-23916 · CVE-2023-23946 · CVE-2023-24329 · CVE-2023-24532 · CVE-2023-24534 · CVE-2023-2483 · CVE-2023-24998 · CVE-2023-2513 · CVE-2023-25193 · CVE-2023-25652 · CVE-2023-25690 · CVE-2023-25809 · CVE-2023-25815 · CVE-2023-26048 · CVE-2023-26049 · CVE-2023-2650 · CVE-2023-26545 · CVE-2023-26604 · CVE-2023-27533 · CVE-2023-27534 · CVE-2023-27535 · CVE-2023-27536 · CVE-2023-27538 · CVE-2023-27561 · CVE-2023-2828 · CVE-2023-28320 · CVE-2023-28321 · CVE-2023-28322 · CVE-2023-28328 · CVE-2023-28464 · CVE-2023-28486 · CVE-2023-28487 · CVE-2023-28642 · CVE-2023-28772 · CVE-2023-28840 · CVE-2023-28841 · CVE-2023-28842 · CVE-2023-29007 · CVE-2023-29383 · CVE-2023-29402 · CVE-2023-29406 · CVE-2023-29409 · CVE-2023-2976 · CVE-2023-30630 · CVE-2023-30772 · CVE-2023-31084 · CVE-2023-3138 · CVE-2023-31436 · CVE-2023-31484 · CVE-2023-32269 · CVE-2023-32697 · CVE-2023-33264 · CVE-2023-34034 · CVE-2023-34035 · CVE-2023-34453 · CVE-2023-34454 · CVE-2023-34455 · CVE-2023-34462 · CVE-2023-35116 · CVE-2023-3635 · CVE-2023-36479 · CVE-2023-39533 · CVE-2023-40167 · CVE-2023-40217 · CVE-2023-41105 · CVE-2023-41900 · CVE-2023-43642 · CVE-2023-43804 · CVE-2023-44487 · CVE-2023-45803 · CVE-2024-21626

Source published
Apr 4, 2023, 9:12:17 PM (timezone not stated)
Source modified
Feb 13, 2025, 4:48:54 PM (timezone not stated)
Saved here
18 Nov 2026 04:34:38 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

EUVD CVSS 3.1 · 6.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N

nvd · CVE-2023-28841

Published

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

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-311 · CWE-636 · CWE-755

Original publisher date fields

published: 2023-04-04T22:15:07.937

lastModified: 2026-06-17T05:48:53.467

1 source CPE criteria · context only
  • cpe:2.3:a:mobyproject:moby:*:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published
4 Apr 2023 22:15:07 UTC
Source modified
17 Jun 2026 05:48:53 UTC
Saved here
24 Oct 2026 22:17:10 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · [email protected] · Secondary · 6.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N

CVSS 3.1 · [email protected] · Primary · 6.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N

osv · GHSA-33pg-m6jh-5237

Published

[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*. 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](https://github.com/moby/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](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. Encrypted 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. When 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. An [iptables rule](https://github.com/moby/libnetwork/blob/d9fae4c73daf76c3b0f77e14b45b8bf612ba764d/drivers/overlay/encryption.go#L205-L207) designates outgoing VXLAN datagrams with a VNI that corresponds to an encrypted overlay network for IPsec encapsulation. On Red Hat Enterprise Linux and derivatives such as CentOS and Rocky, the `xt_u32` module has been: * [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) * [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) * [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) This rule is not created when `xt_u32` is unavailable, even though the container is still attached to the network. ## Impact Encrypted overlay networks on affected platforms silently transmit unencrypted data. As a result, `overlay` networks may appear to be functional, passing traffic as expected, but without any of the expected confidentiality or data integrity guarantees. It is possible for an attacker sitting in a trusted position on the network to read all of the application traffic that is moving across the overlay network, resulting in unexpected secrets or user data disclosure. Thus, because many database protocols, internal APIs, etc. are not protected by a second layer of encryption, a user may rely on Swarm encrypted overlay networks to provide confidentiality, which due to this vulnerability is no longer guaranteed. ## Patches Patches are available in Moby releases 23.0.3, and 20.10.24. As Mirantis Container Runtime's 20.10 releases are numbered differently, users of that platform should update to 20.10.16. ## Workarounds * Close the VXLAN port (by default, UDP port 4789) to outgoing traffic at the Internet boundary (see [GHSA-vwm3-crmr-xfxw](https://github.com/moby/moby/security/advisories/GHSA-vwm3-crmr-xfxw)) in order to prevent unintentionally leaking unencrypted traffic over the Internet. * Ensure that the `xt_u32` kernel module is available on all nodes of the Swarm cluster. ## Background * [#43382 ](https://github.com/moby/moby/issues/43382)partially discussed this concern, but did not consider the security implications. * 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. * [#45118](https://github.com/moby/moby/pull/45118) is the ancestor of the final patches, and was where the security implications were discovered. ## Related * [CVE-2023-28840: Encrypted overlay network may be unauthenticated](https://github.com/moby/moby/security/advisories/GHSA-232p-vwff-86mp) * [CVE-2023-28842: Encrypted overlay network with a single endpoint is unauthenticated](https://github.com/moby/moby/security/advisories/GHSA-6wrf-mxfj-pf5p) * [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) * [GHSA-gvm4-2qqg-m333: Security issues in encrypted overlay networks](https://github.com/moby/libnetwork/security/advisories/GHSA-gvm4-2qqg-m333) (libnetwork)

Source published
4 Apr 2023 21:12:20 UTC
Source modified
10 Sep 2026 03:49:53 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS_V3 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N

Publisher rating · MODERATE

osv · GO-2023-1700

Published

Docker Swarm encrypted overlay network traffic may be unencrypted in github.com/docker/docker

Source published
20 Aug 2024 20:29:19 UTC
Source modified
4 Feb 2026 04:22:01 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 04:49 UTC · 273 of 275 readable · 269 fully read · documentation 469/469 current