github.com/edgelesssys/constellation/v2
Affected
- introduced
0, fixed2.16.3(semver)
Fixed versions
2.16.3
Fix
- Fixed version
2.16.3go get github.com/edgelesssys/constellation/[email protected]
Advisory
Also known as: GO-2024-2727
Constallation has pods exposed to peers in VPC
Impact
Cilium allows outside actors (world entity) to directly access pods with their internal pod IP, even if they are not exposed explicitly (e.g. via LoadBalancer). A pod that does not authenticate clients and that does not exclude world traffic via network policy may leak sensitive data to an attacker _inside the cloud VPC_.
Patches
The issue has been patched in v2.16.3.
Workarounds
This network policy excludes all world traffic. It mitigates the problem, but will also block all desired external traffic. If vulnerable pods are known, a policy can be crafted to only firewall those instead (see also https://docs.cilium.io/en/stable/security/policy/language/#access-to-from-outside-cluster).
apiVersion: "cilium.io/v2"
kind: CiliumClusterwideNetworkPolicy
metadata:
name: "from-world-to-role-public"
spec:
endpointSelector:
matchLabels: {}
# role: public
ingressDeny:
- fromEntities:
- world
References
The tracking bug for a Cilium-side fix is https://github.com/cilium/cilium/issues/25626.
High Basis: The source's own band: HIGH
0, fixed 2.16.3 (semver)2.16.3
2.16.3go get github.com/edgelesssys/constellation/[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