CVE-2022-29179 json
Improper Privilege Management in Cilium
published 2022-05-20 4 y ago modified 2026-09-10 1 mo ago also BIT-cilium-2022-29179 , BIT-cilium-operator-2022-29179 , BIT-cilium-proxy-2022-29179 , BIT-hubble-2022-29179 , BIT-hubble-relay-2022-29179 , BIT-hubble-ui-2022-29179 , BIT-hubble-ui-backend-2022-29179 , EUVD-2022-3809 , GHSA-fmrf-gvjp-5j5g , GO-2022-0458
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 30%
- public exploits
- 0
- none known
Summary
Cilium is open source software for providing and securing network connectivity and loadbalancing between application workloads. Prior to versions 1.9.16, 1.10.11, and 1.11.15, if an attacker is able to perform a container escape of a container running as root on a host where Cilium is installed, the attacker can escalate privileges to cluster admin by using Cilium's Kubernetes service account. The problem has been fixed and the patch is available in versions 1.9.16, 1.10.11, and 1.11.5. There are no known workarounds available.
Patch / fix
- go github.com/cilium/cilium 1.9.16, 1.10.11, 1.11.5
- bitnami cilium 1.9.16, 1.10.11, 1.11.5
- bitnami cilium-operator 1.9.16, 1.10.11, 1.11.5
- bitnami cilium-proxy 1.9.16, 1.10.11, 1.11.5
- bitnami hubble 1.9.16, 1.10.11, 1.11.5
- bitnami hubble-relay 1.9.16, 1.10.11, 1.11.5
- bitnami hubble-ui 1.9.16, 1.10.11, 1.11.5
- bitnami hubble-ui-backend 1.9.16, 1.10.11, 1.11.5
- cilium cilium 1.9.16, 1.10.11, 1.11.5
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 18 mo ago
Exploit prediction
0.36% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H |
| NVD | 3.1 | 8.2 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H |
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
| OSV | 3.1 | 8.2 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/cilium/cilium | >=1.11.0, <1.11.5 >=1.10.0, <1.10.11 <1.9.16 |
1.11.5 1.10.11 1.9.16 |
| bitnami | cilium | <1.9.16 >=1.10.0, <1.10.11 >=1.11.0, <1.11.5 |
1.9.16 1.10.11 1.11.5 |
| bitnami | cilium-operator | <1.9.16 >=1.10.0, <1.10.11 >=1.11.0, <1.11.5 |
1.9.16 1.10.11 1.11.5 |
| bitnami | cilium-proxy | <1.9.16 >=1.10.0, <1.10.11 >=1.11.0, <1.11.5 |
1.9.16 1.10.11 1.11.5 |
| bitnami | hubble | <1.9.16 >=1.10.0, <1.10.11 >=1.11.0, <1.11.5 |
1.9.16 1.10.11 1.11.5 |
| bitnami | hubble-relay | <1.9.16 >=1.10.0, <1.10.11 >=1.11.0, <1.11.5 |
1.9.16 1.10.11 1.11.5 |
| bitnami | hubble-ui | <1.9.16 >=1.10.0, <1.10.11 >=1.11.0, <1.11.5 |
1.9.16 1.10.11 1.11.5 |
| bitnami | hubble-ui-backend | <1.9.16 >=1.10.0, <1.10.11 >=1.11.0, <1.11.5 |
1.9.16 1.10.11 1.11.5 |
Affected products
- cilium cilium
Classification
- Weakness
-
- CWE-269 Improper Privilege Management
References
-
github.com
/cilium/cilium/releases/tag/v1.10.11
web, release-notes, third-party-advisory, advisory
-
github.com
/cilium/cilium/releases/tag/v1.11.5
web, release-notes, third-party-advisory, advisory
-
github.com
/cilium/cilium/releases/tag/v1.9.16
web, release-notes, third-party-advisory, advisory
-
github.com
/cilium/cilium/security/advisories/GHSA-fmrf-gvjp-5j5g
web, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-29179
advisory, web
Sources
- CVE List CVE-2022-29179
- GitHub Advisory GHSA-fmrf-gvjp-5j5g
- NVD CVE-2022-29179
- OSV BIT-cilium-2022-29179
- OSV BIT-cilium-operator-2022-29179
- OSV BIT-cilium-proxy-2022-29179
- OSV BIT-hubble-2022-29179
- OSV BIT-hubble-relay-2022-29179
- OSV BIT-hubble-ui-2022-29179
- OSV BIT-hubble-ui-backend-2022-29179
- OSV GO-2022-0458
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.