CVE-2023-28114 json
`cilium-cli` disables etcd authorization for clustermesh clusters
published 3y ago modified 2mo ago also GHSA-6f27-3p6c-p5jc , GO-2023-1653 , EUVD-2023-0902
- cvss
- 4.8
- 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 8%
- public exploits
- 0
- none known
Summary
`cilium-cli` is the command line interface to install, manage, and troubleshoot Kubernetes clusters running Cilium. Prior to version 0.13.2,`cilium-cli`, when used to configure cluster mesh functionality, can remove the enforcement of user permissions on the `etcd` store used to mirror local cluster information to remote clusters. Users who have set up cluster meshes using the Cilium Helm chart are not affected by this issue.
Due to an incorrect mount point specification, the settings specified by the `initContainer` that configures `etcd` users and their permissions are overwritten when using `cilium-cli` to configure a cluster mesh. An attacker who has already gained access to a valid key and certificate for an `etcd` cluster compromised in this manner could then modify state in that `etcd` cluster.
This issue is patched in `cilium-cli` 0.13.2. As a workaround, one may use Cilium's Helm charts to create their cluster.
Patch / fix
- go github.com/cilium/cilium-cli 0.13.2
- cilium cilium-cli 0.13.2
Is CVE-2023-28114 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
- partial
- Assessed
- last yr.
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-15).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.8 | CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N |
| NVD | 3.1 | 4.1 | CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N |
| GitHub | 3.1 | 4.8 | CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/cilium/cilium-cli | <0.13.2 |
0.13.2 |
Affected products
- cilium cilium-cli
Classification
References
-
github.com
/cilium/cilium-cli/commit/fb1427025764e1eebc4a7710d902c4f22cae2610
web, patch
-
github.com
/cilium/cilium-cli/security/advisories/GHSA-6f27-3p6c-p5jc
web, vendor-advisory, advisory
-
artifacthub.io
/packages/helm/cilium/cilium
web, product
-
github.com
/cilium/cilium-cli/releases/tag/v0.13.2
web, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2023-28114
advisory
-
github.com
/cilium/cilium-cli
package
Sources
- CVE List CVE-2023-28114
- GitHub Advisory GHSA-6f27-3p6c-p5jc
- NVD CVE-2023-28114
- OSV GO-2023-1653
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.