github.com/cilium/cilium
Affected
- introduced
1.13.0, fixed1.13.7(semver)
Fixed versions
1.13.7
Fix
- Fixed version
1.13.7go get github.com/cilium/[email protected]
Advisory
Also known as: BIT-cilium-2023-39347, BIT-cilium-operator-2023-39347, BIT-cilium-proxy-2023-39347, BIT-hubble-2023-39347, BIT-hubble-relay-2023-39347, BIT-hubble-ui-2023-39347, BIT-hubble-ui-backend-2023-39347, CVE-2023-39347, GO-2023-2078
Kubernetes users may update Pod labels to bypass network policy
Impact
An attacker with the ability to update pod labels can cause Cilium to apply incorrect network policies.
This issue arises due to the fact that on pod update, Cilium incorrectly uses user-provided pod labels to select the policies which apply to the workload in question.
This can affect:
Non-existent construct names can be provided, which bypass all network policies applicable to the construct. For example, providing a pod with a non-existent namespace as the value of the io.kubernetes.pod.namespace label results in none of the namespaced CiliumNetworkPolicies applying to the pod in question.
This attack requires the attacker to have Kubernetes API Server access, as described in the Cilium Threat Model.
Patches
This issue affects:
This issue has been resolved in:
Workarounds
An admission webhook can be used to prevent pod label updates to the k8s:io.kubernetes.pod.namespace and io.cilium.k8s.policy.* keys.
Acknowledgements
The Cilium community has worked together with members of Palantir and Isovalent to prepare these mitigations. Special thanks to @odinuge for reporting this issue and to @nebril for the fix.
For more information
If you have any questions or comments about this advisory, please reach out on Slack.
If you think you have found a vulnerability in Cilium, we strongly encourage you to report it to our private security mailing list – [[email protected]](mailto:[email protected]) – 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.
Medium Basis: The source's own band: MODERATE
1.13.0, fixed 1.13.7 (semver)1.13.7
1.13.7go get github.com/cilium/[email protected]1.14.0, fixed 1.14.2 (semver)1.14.2
1.14.2go get github.com/cilium/[email protected]0, fixed 1.12.14 (semver)1.12.14
1.12.14go get github.com/cilium/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0