CVE-2024-25630 json
Cilium has unencrypted ingress/health traffic when using Wireguard transparent encryption
published 2024-02-20 2 y ago modified 2026-09-10 1 mo ago also BIT-cilium-2024-25630 , BIT-cilium-operator-2024-25630 , BIT-cilium-proxy-2024-25630 , BIT-hubble-2024-25630 , BIT-hubble-relay-2024-25630 , BIT-hubble-ui-2024-25630 , BIT-hubble-ui-backend-2024-25630 , EUVD-2024-0547 , GHSA-7496-fgv9-xw82 , GO-2024-2568
- 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 7%
- public exploits
- 0
- none known
Summary
Cilium is a networking, observability, and security solution with an eBPF-based dataplane. For Cilium users who are using CRDs to store Cilium state (the default configuration) and Wireguard transparent encryption, traffic to/from the Ingress and health endpoints is not encrypted. This issue affects Cilium v1.14 before v1.14.7 and has been patched in Cilium v1.14.7. There is no workaround to this issue.
Patch / fix
- go github.com/cilium/cilium 1.14.7
- bitnami cilium 1.14.7
- bitnami cilium-operator 1.14.7
- bitnami cilium-proxy 1.14.7
- bitnami hubble 1.14.7
- bitnami hubble-relay 1.14.7
- bitnami hubble-ui 1.14.7
- bitnami hubble-ui-backend 1.14.7
- cilium cilium 1.14.7
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% 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 | 5.3 | CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/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.7 |
1.14.7 |
| bitnami | cilium | >=1.14.0, <1.14.7 |
1.14.7 |
| bitnami | cilium-operator | >=1.14.0, <1.14.7 |
1.14.7 |
| bitnami | cilium-proxy | >=1.14.0, <1.14.7 |
1.14.7 |
| bitnami | hubble | >=1.14.0, <1.14.7 |
1.14.7 |
| bitnami | hubble-relay | >=1.14.0, <1.14.7 |
1.14.7 |
| bitnami | hubble-ui | >=1.14.0, <1.14.7 |
1.14.7 |
| bitnami | hubble-ui-backend | >=1.14.0, <1.14.7 |
1.14.7 |
Affected products
- cilium cilium
Classification
References
-
github.com
/cilium/cilium/security/advisories/GHSA-7496-fgv9-xw82
web, vendor-advisory, advisory
-
docs.cilium.io
/en/stable/security/network/encryption-wireguard/#encryption-wg
web, product
-
github.com
/cilium/cilium/releases/tag/v1.14.7
web, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2024-25630
advisory
-
github.com
/cilium/cilium
package
Sources
- CVE List CVE-2024-25630
- GitHub Advisory GHSA-7496-fgv9-xw82
- NVD CVE-2024-25630
- OSV BIT-cilium-2024-25630
- OSV BIT-cilium-operator-2024-25630
- OSV BIT-cilium-proxy-2024-25630
- OSV BIT-hubble-2024-25630
- OSV BIT-hubble-relay-2024-25630
- OSV BIT-hubble-ui-2024-25630
- OSV BIT-hubble-ui-backend-2024-25630
- OSV GO-2024-2568
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.