Skip to content
Fencer Vulns
medium 6.1

CVE-2024-28250 json

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

published 2024-03-18 2 y ago modified 2026-09-10 1 mo ago also BIT-cilium-2024-28250 , BIT-cilium-operator-2024-28250 , BIT-cilium-proxy-2024-28250 , BIT-hubble-2024-28250 , BIT-hubble-relay-2024-28250 , BIT-hubble-ui-2024-28250 , BIT-hubble-ui-backend-2024-28250 , EUVD-2024-1011 , GHSA-v6q2-4qr3-5cw6 , GO-2024-2657

cvss
6.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 6%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/cilium/cilium 1.14.8, 1.15.2
  • bitnami cilium 1.14.8, 1.15.2
  • bitnami cilium-operator 1.14.8, 1.15.2
  • bitnami cilium-proxy 1.14.8, 1.15.2
  • bitnami hubble 1.14.8, 1.15.2
  • bitnami hubble-relay 1.14.8, 1.15.2
  • bitnami hubble-ui 1.14.8, 1.15.2
  • bitnami hubble-ui-backend 1.14.8, 1.15.2
  • cilium cilium 1.14.8, 1.15.2

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 6.1 CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
GitHub 3.1 6.1 CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
NVD 3.1 6.1 CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
OSV 3.1 6.1 CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/cilium/cilium
>=1.14.0, <1.14.8
>=1.15.0, <1.15.2
1.14.8
1.15.2
bitnami cilium
>=1.14.0, <1.14.8
>=1.15.0, <1.15.2
1.14.8
1.15.2
bitnami cilium-operator
>=1.14.0, <1.14.8
>=1.15.0, <1.15.2
1.14.8
1.15.2
bitnami cilium-proxy
>=1.14.0, <1.14.8
>=1.15.0, <1.15.2
1.14.8
1.15.2
bitnami hubble
>=1.14.0, <1.14.8
>=1.15.0, <1.15.2
1.14.8
1.15.2
bitnami hubble-relay
>=1.14.0, <1.14.8
>=1.15.0, <1.15.2
1.14.8
1.15.2
bitnami hubble-ui
>=1.14.0, <1.14.8
>=1.15.0, <1.15.2
1.14.8
1.15.2
bitnami hubble-ui-backend
>=1.14.0, <1.14.8
>=1.15.0, <1.15.2
1.14.8
1.15.2

Affected products

  • cilium cilium

Classification

Weakness
  • CWE-311 Missing Encryption of Sensitive Data
  • CWE-319 Cleartext Transmission of Sensitive Information

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.