Cyber Resilience

CVE-2023-28840

Mobyproject Moby 1.12.0 – 20.10.24

Public PoC
Published
04 April 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:L
EPSS Score 0.027 85th percentile
Risk Priority 59 floored blend · peak EPSS

Summary

CVE-2023-28840 is a high-severity Unprotected Alternate Channel (CWE-420) vulnerability in Mobyproject Moby. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Fallback Channels (T1008); ranked in the top 15% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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*.…

more

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1008 Fallback Channels Command And Control
Adversaries may use fallback or alternate communication channels if the primary channel is compromised or inaccessible in order to maintain reliable command and control and to avoid data transfer thresholds.
T1048 Exfiltration Over Alternative Protocol Exfiltration
Adversaries may steal data by exfiltrating it over a different protocol than that of the existing command and control channel.
T1048.003 Exfiltration Over Unencrypted Non-C2 Protocol Exfiltration
Adversaries may steal data by exfiltrating it over an un-encrypted network protocol other than that of the existing command and control channel.
T1087 Account Discovery Discovery
Adversaries may attempt to get a listing of valid accounts, usernames, or email addresses on a system or within a compromised environment.
T1110 Brute Force Credential Access
Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-28842Same product: Mobyproject Moby
CVE-2023-28841Same product: Mobyproject Moby
CVE-2024-36620Same product: Mobyproject Moby
CVE-2024-24557Same product: Mobyproject Moby
CVE-2025-54388Same product: Mobyproject Moby
CVE-2024-36623Same product: Mobyproject Moby
CVE-2024-29018Same product: Mobyproject Moby
CVE-2025-54410Same product: Mobyproject Moby
CVE-2024-36621Same product: Mobyproject Moby
CVE-2024-32473Same product: Mobyproject Moby

Affected Assets

mobyproject
moby
1.12.0 — 20.10.24 · 23.0.0 — 23.0.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 2 hardening rules · 2 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V3.2.1
  • V7.4.1
  • V8.3.3
  • V10.3.4

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-636 CWE-755

Supports failing securely by requiring alerts and configurable actions (e.g., shutdown) when the audit mechanism fails instead of continuing without it.

addresses: CWE-636 CWE-755

Entering safe mode when conditions are detected prevents failing open and continuing normal operation in a potentially exploitable state.

addresses: CWE-636 CWE-755

Directly requires transition to a known (secure) state on failure, preventing fail-open behavior.

addresses: CWE-636 CWE-755

Standby components and explicit exchange criteria enforce a controlled, secure failover instead of failing open.

addresses: CWE-636 CWE-755

Directly implements fail-safe (fail-closed/secure) behavior on indicated failures, preventing the system from defaulting to an insecure open state.

addresses: CWE-420

Usage restrictions and authorization for remote access protect against unprotected alternate channels.

addresses: CWE-636

Ensures audit logging continues on primary failure instead of failing open with no logging capability.

addresses: CWE-636

Ensures security functions remain enforced via alternatives instead of defaulting to an insecure state when the primary means fails.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.DS-02 mostly match
prevents

Protecting all data-in-transit directly mitigates unequal channel protection though the control addresses broader transit scenarios.

PR.IR-01 mostly match
prevents

Network protection from unauthorized access inherently requires securing every channel, not just primaries.

PR.PS-06 mostly match
prevents

Secure-development practices explicitly include designing error and failure handling to remain in a secure state.

DE.CM-01 partial match
prevents

Network monitoring can surface use of unprotected alternate channels but does not prevent the design flaw.

PR.AA-05 partial match
prevents

Least-privilege policy and enforcement directly counters the permissive-access fallback example in the CWE.

PR.PS-01 partial match
prevents

Hardened baselines and configuration management reduce the chance that error paths default to insecure settings.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development and acceptance verifies correct handling of exceptional conditions.

prevents

Access restrictions may cover primary paths but leave alternate channels unprotected unless explicitly extended.

prevents

Secure authentication applies to primary channels but does not ensure alternate channels receive the same strength.

degrades

Documented operating procedures may specify exception handling but do not guarantee implementation.

A.8.15 Logging partial match
finds

Logging captures unhandled exceptions, aiding detection but not preventing the weakness.

finds

Monitoring can surface unhandled exceptions but does not enforce proper handling.

References