# CVE-2023-28114: Cilium-cli vulnerability exposes Kubernetes clusters to unauthorized access via etcd, impacting versions prior to 0.13.2.
This CVE record highlights a vulnerability in
cilium-cli
that disables etcd authorization for clustermesh clusters, impacting versions prior to 0.13.2.
Understanding CVE-2023-28114
This vulnerability in
cilium-cli
exposes clusters running Cilium to unauthorized access by disabling permissions on the etcd
store.
What is CVE-2023-28114?
The
cilium-cli
tool, a command line interface for managing Kubernetes clusters with Cilium, fails to enforce user permissions on the etcd
store when configuring cluster mesh functionality. This can allow attackers with access to compromised etcd
clusters to modify cluster state.
The Impact of CVE-2023-28114
With this vulnerability, unauthorized users could potentially manipulate sensitive data within
etcd
, leading to data breaches or unauthorized access to Kubernetes clusters.
Technical Details of CVE-2023-28114
This section provides a deeper look into the vulnerability, affected systems, and exploitation mechanism.
Vulnerability Description
The issue arises due to an incorrect mount point specification in
cilium-cli
, causing the etcd
user permissions set by the initContainer
to be overwritten, thereby compromising cluster security.
Affected Systems and Versions
Versions of
cilium-cli
prior to 0.13.2 are impacted by this vulnerability, with cluster mesh functionality being particularly susceptible.
Exploitation Mechanism
By exploiting the vulnerability in
cilium-cli
, unauthorized users can bypass etcd
authorization, potentially gaining the ability to make unauthorized changes to cluster states.
Mitigation and Prevention
To address CVE-2023-28114, immediate actions and long-term security practices can be implemented to mitigate risks and prevent further exploitation.
Immediate Steps to Take
Users are advised to update
cilium-cli
to version 0.13.2 or above to patch the vulnerability. Alternatively, utilizing Cilium's Helm charts to set up clusters can circumvent the issue.
Long-Term Security Practices
Implement strong access controls, regularly monitor cluster activities, and conduct security audits to identify and address any vulnerabilities proactively.
Patching and Updates
Regularly check for security updates and patches for all software components within Kubernetes clusters to ensure the ongoing security of the environment.