GHSA-4hc4-pgfx-3mrx BIT-cilium-2023-27593 BIT-cilium-operator-2023-27593 BIT-cilium-proxy-2023-27593 BIT-hubble-2023-27593 BIT-hubble-relay-2023-27593 BIT-hubble-ui-2023-27593 BIT-hubble-ui-backend-2023-27593 CVE-2023-27593
cilium-agent container can access the host via `hostPath` mount
- Severity
- 4.4 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.22%
- Chance of exploitation in the next 30 days. Higher than 12.17% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-276 Incorrect Default Permissions
- Fix
1.11.15- Upgrade github.com/cilium/cilium to this version or later
Description
Impact
An attacker with access to a Cilium agent pod can write to /opt/cni/bin due to a hostPath mount of that directory in the agent pod. By replacing the CNI binary with their own malicious binary and waiting for the creation of a new pod on the node, the attacker can gain access to the underlying node.
Patches
The issue has been fixed and is available on versions >=1.11.15, >=1.12.8, >=1.13.1.
Workarounds
Kubernetes RBAC should be used to deny users and service accounts exec access to Cilium agent pods.
In cases where a user requires exec access to Cilium agent pods, but should not have access to the underlying node, no workaround is possible.
References
Acknowledgements
The Cilium community has worked together with members of Isovalent and Form3 to prepare these mitigations. Special thanks to Anastasios Koutlis, Daniel Teixeira, and Magdalena Oczadly for their cooperation.
For more information
If you have any questions or comments about this advisory, please reach out on Slack.
As usual, if you think you found a related vulnerability, we strongly encourage you to report security vulnerabilities to our private security mailing list: security@cilium.io - first, before disclosing them in any public forums. This is a private mailing list where only members of the Cilium internal security team are subscribed to, and is treated as top priority.
Affected versions
Go
| Package | Vulnerable | Fixed in |
|---|---|---|
| github.com/cilium/cilium | < 1.11.15 |
1.11.15 |
| github.com/cilium/cilium | >= 1.12.0, < 1.12.8 |
1.12.8 |
| github.com/cilium/cilium | >= 1.13.0, < 1.13.1 |
1.13.1 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
github.com/cilium/cilium Go → 1.11.15
- go
go get github.com/cilium/cilium@v1.11.15 && go mod tidy
Severity breakdown
CVSS 3.1 4.4
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Weakness
CWE-276: Incorrect Default Permissions
During installation, installed file permissions are set to allow anyone to modify those files.
How to prevent it
- Architecture and Design, Operation: The architecture needs to access and modification attributes for files to only those users who actually require those actions.
- Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-fm8w-2m5w-9j7r Cilium may unexpectedly allow ingress traffic from the local namespace when a Kubernetes NetworkPolicy is configured with an ipBlock match | Medium | Also affects github.com/cilium/cilium |
| GHSA-w7c2-w76w-5hmj Cilium: Namespaced HTTPRoutes can redirect traffic to other namespaces | High | Also affects github.com/cilium/cilium |
| GHSA-q6h5-q3q6-f87x CiliumLocalRedirectPolicy addressMatcher allows cross-namespace service traffic hijacking and can break service translation | Medium | Also affects github.com/cilium/cilium |
| GHSA-3fcv-jvfp-m4q9 Cilium vulnerable to sensitive information disclosure and cluster disruption via local Envoy admin socket access | High | Also affects github.com/cilium/cilium |
| GHSA-gj49-89wh-h4gj Cillium exposes sensitive information included in the cilium-bugtool debug archive | Medium | Also affects github.com/cilium/cilium |
| GHSA-hxv8-4j4r-cqgv Cilium L7 proxy may bypass Kubernetes NetworkPolicy for same-node traffic | Medium | Also affects github.com/cilium/cilium |
| GHSA-5r23-prx4-mqg3 Cilium may not enforce host firewall policies when Native Routing, WireGuard and Node Encryption are enabled | Medium | Also affects github.com/cilium/cilium |
| GHSA-38pp-6gcp-rqvm Cilium with misconfigured toGroups in policies can lead to unrestricted egress traffic | Medium | Also affects github.com/cilium/cilium |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor