Skip to content
Fencer Vulns
high 8.0

CVE-2024-28860 json

Insecure IPsec transport encryption in Cilium

published 2024-03-27 2 y ago modified 2026-09-10 1 mo ago also BIT-cilium-2024-28860 , BIT-cilium-operator-2024-28860 , BIT-cilium-proxy-2024-28860 , BIT-hubble-2024-28860 , BIT-hubble-relay-2024-28860 , BIT-hubble-ui-2024-28860 , BIT-hubble-ui-backend-2024-28860 , EUVD-2024-0984 , GHSA-pwqm-x5x6-5586 , GO-2024-2666

cvss
8.0
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. Users of IPsec transparent encryption in Cilium may be vulnerable to cryptographic attacks that render the transparent encryption ineffective. In particular, Cilium is vulnerable to chosen plaintext, key recovery, replay attacks by a man-in-the-middle attacker. These attacks are possible due to an ESP sequence number collision when multiple nodes are configured with the same key. Fixed versions of Cilium use unique keys for each IPsec tunnel established between nodes, resolving all of the above attacks. This vulnerability is fixed in 1.13.13, 1.14.9, and 1.15.3.

Patch / fix

  • go github.com/cilium/cilium 1.13.14, 1.14.9, 1.15.3
  • bitnami cilium 1.14.9, 1.15.3
  • bitnami cilium-operator 1.14.9, 1.15.3
  • bitnami cilium-proxy 1.13.14, 1.14.9, 1.15.3
  • bitnami hubble 1.13.14, 1.14.9, 1.15.3
  • bitnami hubble-relay 1.14.9, 1.15.3
  • bitnami hubble-ui 1.13.14, 1.14.9, 1.15.3
  • bitnami hubble-ui-backend 1.13.14, 1.14.9, 1.15.3
  • cilium cilium 1.14.9, 1.15.3

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
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 8.0 CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
GitHub 3.1 8.0 CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
NVD 3.1 6.8 CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
OSV 3.1 8.0 CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N

Affected packages

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

Affected products

  • cilium cilium

Classification

Weakness
  • CWE-326 Inadequate Encryption Strength

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.