CVE-2023-28841

MEDIUMNVD 6.86.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 6.8 from GitHub Security Advisory (severity: MODERATE) published 2023-04-04. NVD baseline CVSS 6.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2023-1167 (ENISA EUVD) · GHSA-33pg-m6jh-5237 (GitHub Security Advisories)Source: ENISA EUVD

6.8EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 6.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
6.8
EG Score
6.8MEDIUMmedium confidence
EG Risk
31
EG Risk 31/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity68% × 45%
Impact severity (EG Severity): CVSS 6.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
52nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.8): severity, escalated by confirmed exploitation. This CVE's 6.8 is its impact severity (EG Severity), not escalated.

EG Severity
6.8 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 4, 2023

Last Modified

November 21, 2024

Advisory Details (10)

Auto-updated Oct 24, 2026
Patch available. Sources: github, github_pr.
Web page

[SECURITY] Fedora 39 Update: moby-engine-24.0.5-1.fc39 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XNF4OLYZRQE75EB5TW5N42FSXHBXGWFE/
Web page

[SECURITY] Fedora 37 Update: moby-engine-24.0.5-1.fc37 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LYZOKMMVX4SIEHPJW3SJUQGMO5YZCPHC/
GitHub advisoryMentions a patch (unverified)

The Swarm VXLAN port may be exposed to attack due to ambiguous documentation · Advisory · moby/moby · GitHub

https://github.com/moby/moby/security/advisories/GHSA-vwm3-crmr-xfxw
GitHub advisoryMentions a patch (unverified)

Encrypted overlay network with a single endpoint is unauthenticated · Advisory · moby/moby · GitHub

https://github.com/moby/moby/security/advisories/GHSA-6wrf-mxfj-pf5p
GitHub advisoryMentions a patch (unverified)

Encrypted overlay network traffic may be unencrypted · Advisory · moby/moby · GitHub

https://github.com/moby/moby/security/advisories/GHSA-33pg-m6jh-5237
GitHub advisoryMentions a patch (unverified)

Encrypted overlay network may be unauthenticated · Advisory · moby/moby · GitHub

https://github.com/moby/moby/security/advisories/GHSA-232p-vwff-86mp
GitHub pull request

libnetwork: support encrypted overlay networks on systems without xt_u32 kernel module

Upstream fix in progress (PR #45118 · moby/moby, state=closed)

https://github.com/moby/moby/pull/45118
Web page

issues with swarm encrypted overlay network and iptables-nft on RHEL 8+ · Issue #43382 · moby/moby · GitHub

https://github.com/moby/moby/issues/43382
GitHub advisoryMentions a patch (unverified)

Security issues in encrypted overlay networks · Advisory · moby/libnetwork · GitHub

https://github.com/moby/libnetwork/security/advisories/GHSA-gvm4-2qqg-m333
Web page

libnetwork/drivers/overlay/encryption.go at d9fae4c73daf76c3b0f77e14b45b8bf612ba764d · moby/libnetwork · GitHub

https://github.com/moby/libnetwork/blob/d9fae4c73daf76c3b0f77e14b45b8bf612ba764d/drivers/overlay/encryption.go#L205-L207

Vendor Advisories for CVE-2023-28841(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntugolang-github-docker-docker-dev (20.10.25+dfsg1-2ubuntu1+esm2) @ noble2026-10-24ubuntu
redhatmulticluster-engine/work-rhel8:v2.4.4-62024-03-11redhat
gogithub.com/docker/docker @ 20.10.24 (fixes >= 1.12.0, < 20.10.24)—ghsa
gogithub.com/docker/docker @ 23.0.3 (fixes >= 23.0.0, < 23.0.3)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
docker.io20.10.10+dfsg1-1 ... 28.5.2+dfsg4-3 (61 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
docker.io—
  • every version up to 20.10.24+dfsg1-1: fixed in 20.10.24+dfsg1-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
docker.io—
  • every version up to 20.10.24+dfsg1-1: fixed in 20.10.24+dfsg1-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
docker.io—
  • every version up to 20.10.24+dfsg1-1: fixed in 20.10.24+dfsg1-1
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/docker/docker—
  • 1.12.0 up to 20.10.24: fixed in 20.10.24
  • 23.0.0 up to 23.0.3: fixed in 23.0.3
  • 1.12.0 up to 20.10.24+incompatible: fixed in 20.10.24+incompatible
  • 23.0.0+incompatible up to 23.0.3+incompatible: fixed in 23.0.3+incompatible
—

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 9× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 217 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 119 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:39 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  2. 2026-11-01 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  3. 2026-11-01 08:21 UTCGHSA enrichmentGHSA-33pg-m6jh-5237 · GitHub severity MODERATE · GitHub CVSS 6.8
  4. 2026-11-01 08:21 UTCEG score recompute
  5. 2026-10-31 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  6. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  7. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  8. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  9. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  10. 2026-10-26 16:28 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  11. 2026-10-25 17:44 UTCEG score recompute
  12. 2026-10-25 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  13. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  14. 2026-10-24 14:56 UTCEG score recompute
  15. 2026-10-24 14:56 UTCVendor advisory
  16. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  17. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  18. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  19. 2026-10-20 16:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  20. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  21. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  22. 2026-10-18 08:06 UTCEG score recompute
  23. 2026-10-17 16:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  24. 2026-10-16 16:35 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  25. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
Show 73 more
  1. 2026-10-14 16:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  2. 2026-10-14 14:24 UTCOSV refresh
  3. 2026-10-13 16:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  4. 2026-10-12 18:29 UTCEG score recompute
  5. 2026-10-12 16:30 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  6. 2026-10-11 21:55 UTCEG score recompute
  7. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  8. 2026-10-10 19:57 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  9. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  10. 2026-10-08 17:06 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  11. 2026-10-07 23:45 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  12. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  13. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  14. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  15. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  16. 2026-10-02 16:23 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  17. 2026-10-01 19:47 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  18. 2026-09-30 16:21 UTCEG score recompute
  19. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  20. 2026-09-29 15:16 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  21. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  22. 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  23. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  24. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  25. 2026-09-23 16:17 UTCOSV refresh
  26. 2026-09-23 13:45 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  27. 2026-09-22 14:45 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  28. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  29. 2026-09-16 14:05 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  30. 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  31. 2026-09-12 14:58 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  32. 2026-09-11 14:50 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  33. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  34. 2026-09-08 21:57 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  35. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  36. 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  37. 2026-09-05 15:25 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  38. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  39. 2026-09-04 10:59 UTCOSV refresh
  40. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  41. 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  42. 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  43. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  44. 2026-08-30 01:19 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  45. 2026-08-28 21:38 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  46. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  47. 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  48. 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  49. 2026-08-24 14:14 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  50. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  51. 2026-08-21 23:46 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  52. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  53. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  54. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  55. 2026-08-17 21:30 UTCOSV refresh
  56. 2026-08-17 13:44 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  57. 2026-08-16 14:53 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  58. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  59. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  60. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  61. 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  62. 2026-08-11 13:39 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  63. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  64. 2026-08-08 16:34 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  65. 2026-08-07 16:24 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  66. 2026-08-06 13:44 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  67. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  68. 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  69. 2026-08-04 10:35 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  70. 2026-08-03 10:34 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  71. 2026-08-02 17:27 UTCOSV refresh
  72. 2026-08-02 02:24 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  73. 2026-08-01 04:13 UTCEPSS rescoreEPSS 0.7% · 49th percentile

Frequently asked(5)

What is CVE-2023-28841?
CVE-2023-28841 is a medium-severity vulnerability; its CVE record was published on April 4, 2023. 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…
When was the CVE record for CVE-2023-28841 published?
The CVE record for CVE-2023-28841 was published on April 4, 2023. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2023-28841 actively exploited?
CVE-2023-28841 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-28841?
CVE-2023-28841 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2023-28841?
A fix for CVE-2023-28841 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-28841 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-28841

Explore →

Is Your Infrastructure Affected by CVE-2023-28841?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.