Skip to content
Fencer Vulns
low 2.6

CVE-2023-30851 json

Potential HTTP policy bypass when using header rules in Cilium

published 2023-05-22 3 y ago modified 2026-09-10 1 mo ago also BIT-cilium-2023-30851 , BIT-cilium-operator-2023-30851 , BIT-cilium-proxy-2023-30851 , BIT-hubble-2023-30851 , BIT-hubble-relay-2023-30851 , BIT-hubble-ui-2023-30851 , BIT-hubble-ui-backend-2023-30851 , EUVD-2023-1449 , GHSA-2h44-x2wx-49f4 , GO-2023-1785

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

Summary

Cilium is a networking, observability, and security solution with an eBPF-based dataplane. This issue only impacts users who have a HTTP policy that applies to multiple `toEndpoints` AND have an allow-all rule in place that affects only one of those endpoints. In such cases, a wildcard rule will be appended to the set of HTTP rules, which could cause bypass of HTTP policies. This issue has been patched in Cilium 1.11.16, 1.12.9, and 1.13.2.

Patch / fix

  • go github.com/cilium/cilium 1.11.16, 1.12.9, 1.13.2
  • bitnami cilium 1.11.16, 1.12.9, 1.13.2
  • bitnami cilium-operator 1.11.16, 1.12.9, 1.13.2
  • bitnami cilium-proxy 1.11.16, 1.12.9, 1.13.2
  • bitnami hubble 1.11.16, 1.12.9, 1.13.2
  • bitnami hubble-relay 1.11.16, 1.12.9, 1.13.2
  • bitnami hubble-ui 1.11.16, 1.12.9, 1.13.2
  • bitnami hubble-ui-backend 1.11.16, 1.12.9, 1.13.2
  • cilium cilium 1.11.16, 1.12.9, 1.13.2

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
21 mo ago

Exploit prediction

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
go github.com/cilium/cilium
<1.11.16
>=1.12.0, <1.12.9
>=1.13.0, <1.13.2
1.11.16
1.12.9
1.13.2
bitnami cilium
<1.11.16
>=1.12.0, <1.12.9
>=1.13.0, <1.13.2
1.11.16
1.12.9
1.13.2
bitnami cilium-operator
<1.11.16
>=1.12.0, <1.12.9
>=1.13.0, <1.13.2
1.11.16
1.12.9
1.13.2
bitnami cilium-proxy
<1.11.16
>=1.12.0, <1.12.9
>=1.13.0, <1.13.2
1.11.16
1.12.9
1.13.2
bitnami hubble
<1.11.16
>=1.12.0, <1.12.9
>=1.13.0, <1.13.2
1.11.16
1.12.9
1.13.2
bitnami hubble-relay
<1.11.16
>=1.12.0, <1.12.9
>=1.13.0, <1.13.2
1.11.16
1.12.9
1.13.2
bitnami hubble-ui
<1.11.16
>=1.12.0, <1.12.9
>=1.13.0, <1.13.2
1.11.16
1.12.9
1.13.2
bitnami hubble-ui-backend
<1.11.16
>=1.12.0, <1.12.9
>=1.13.0, <1.13.2
1.11.16
1.12.9
1.13.2

Affected products

  • cilium cilium

Classification

Weakness
  • CWE-693 Protection Mechanism Failure

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.