VDB

CVE-2024-28250

CVE-2024-28250 PUBLISHED CVSS 6.1 MEDIUM

Cilium has possible unencrypted traffic between nodes when using WireGuard and L7 policies

Reported by github_m · Published March 18, 2024

github.com/cilium/cilium is fixed in 1.15.2 and 1.14.8 (Go Modules)

Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Starting in version 1.14.0 and prior to versions 1.14.8 and 1.15.2, In Cilium clusters with WireGuard enabled and traffic matching Layer 7 policies Wireguard-eligible traffic that is sent between a node's Envoy proxy and pods on other nodes is sent unencrypted and Wireguard-eligible traffic that is sent between a node's DNS proxy and pods on other nodes is sent unencrypted. This issue has been resolved in Cilium 1.14.8 and 1.15.2 in in native routing mode (`routingMode=native`) and in Cilium 1.14.4 in tunneling mode (`routingMode=tunnel`). Not that in tunneling mode, `encryption.wireguard.encapsulate` must be set to `true`. There is no known workaround for this issue.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
github.com/cilium/ciliumGo Modules1.15.2, 1.14.8
hubble-uiChainguard0.13.3-r3, 0.13.3-r1
cilium-1.14Wolfi1.14.8-r0
ciliumcilium1.15.2, 1.14.8

Risk scores

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

Affected products

VendorProductVersions
ciliumcilium>= 1.14.0, < 1.14.8, >= 1.15.0, < 1.15.2
chainguardhubble-ui0, 0
github.comcilium/cilium1.15.0, 1.14.0
wolficilium-1.140
ciliumcilium1.15.0, 1.14.0
wolfihubble-ui0
chainguardhubble-ui-backend0
chainguardcilium-1.140
chainguardhubble-ui-backend-fips0

Timeline

  • Mar 18, 2024 CVE Published
  • Mar 18, 2024 PoC Published (2 in total, the first dated here)
  • Mar 19, 2024 EPSS Score (30 in total, the first dated here)
  • Mar 19, 2024 CVE Updated
  • Oct 4, 2024 Coalition ESS Score (7 in total, the first dated here)
  • Jan 14, 2026 Security Advisory

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2024-28250
vulnetix vdb fixes CVE-2024-28250

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2024-28250/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›