Skip to content
Fencer Intel
high 7.2

CVE-2024-28248 json

Cilium intermittent HTTP policy bypass

published 2y ago modified 2mo ago also BIT-cilium-2024-28248 , BIT-cilium-operator-2024-28248 , BIT-cilium-proxy-2024-28248 , BIT-hubble-2024-28248 , BIT-hubble-relay-2024-28248 , BIT-hubble-ui-2024-28248 , BIT-hubble-ui-backend-2024-28248 , EUVD-2024-0842 , GHSA-68mj-9pjq-mc85 , GO-2024-2653

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

Summary

Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Starting in version 1.13.9 and prior to versions 1.13.13, 1.14.8, and 1.15.2, Cilium's HTTP policies are not consistently applied to all traffic in the scope of the policies, leading to HTTP traffic being incorrectly and intermittently forwarded when it should be dropped. This issue has been patched in Cilium 1.15.2, 1.14.8, and 1.13.13. There are no known workarounds for this issue.

Patch / fix

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

Is CVE-2024-28248 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2y ago

Exploit prediction

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

CVSS scores

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

Affected packages

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

Affected products

  • cilium cilium

Classification

Weakness
  • CWE-693 Protection Mechanism Failure

References

Sources

Fencer Intel 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.