CVE-2023-29002 json
Debug mode leaks confidential data in Cilium
published 3y ago modified 2mo ago also BIT-cilium-2023-29002 , BIT-cilium-operator-2023-29002 , BIT-cilium-proxy-2023-29002 , BIT-hubble-2023-29002 , BIT-hubble-relay-2023-29002 , BIT-hubble-ui-2023-29002 , BIT-hubble-ui-backend-2023-29002 , EUVD-2023-1365 , GHSA-pg5p-wwp8-97g8 , GO-2023-1730
- cvss
- 7.2
- 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 9%
- public exploits
- 0
- none known
Summary
Cilium is a networking, observability, and security solution with an eBPF-based dataplane. When run in debug mode, Cilium will log the contents of the `cilium-secrets` namespace. This could include data such as TLS private keys for Ingress and GatewayAPI resources. An attacker with access to debug output from the Cilium containers could use the resulting output to intercept and modify traffic to and from the affected cluster. Output of the sensitive information would occur at Cilium agent restart, when secrets in the namespace are modified, and on creation of Ingress or GatewayAPI resources. This vulnerability is fixed in Cilium releases 1.11.16, 1.12.9, and 1.13.2. Users unable to upgrade should disable debug mode.
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
Is CVE-2023-29002 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 FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.20% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-15).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N |
| GitHub | 3.1 | 7.2 | CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N |
| NVD | 3.1 | 6.3 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N |
| OSV | 3.1 | 7.2 | CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N |
| OSV | 3.1 | 6.3 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/cilium/cilium | >=1.7.0, <=1.10.0 >=1.11.0, <1.11.16 >=1.12.0, <1.12.9 >=1.13.0, <1.13.2 >=1.7.0, <1.11.16 |
1.11.16 1.12.9 1.13.2 |
| bitnami | cilium | >=1.7.0, <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.7.0, <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.7.0, <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.7.0, <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.7.0, <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.7.0, <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.7.0, <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-532 Insertion of Sensitive Information into Log File
References
-
github.com
/cilium/cilium/security/advisories/GHSA-pg5p-wwp8-97g8
web, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2023-29002
advisory, web
-
github.com
/cilium/cilium
package
Sources
- CVE List CVE-2023-29002
- GitHub Advisory GHSA-pg5p-wwp8-97g8
- NVD CVE-2023-29002
- OSV BIT-cilium-2023-29002
- OSV BIT-cilium-operator-2023-29002
- OSV BIT-cilium-proxy-2023-29002
- OSV BIT-hubble-2023-29002
- OSV BIT-hubble-relay-2023-29002
- OSV BIT-hubble-ui-2023-29002
- OSV BIT-hubble-ui-backend-2023-29002
- OSV GO-2023-1730
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.