GHSA-mw24-f3xh-j3qv Chall-Manager's invalid NetworkPolicy enables a malicious actor to pivot into another namespace

• Go github.com/ctfer-io/chall-manager/deploy: < 0.6.5 → fixed in 0.6.5 • Go github.com/ctfer-io/chall-manager/sdk: < 0.6.5 → fixed in 0.6.5

Impact Due to a mis-written NetworkPolicy, a malicious actor can pivot from an instance to any Pod out of the origin namespace. This breaks the security-by-default property expected as part of the deployment program, leading to a potential lateral movement. In the specific case of `sdk/kubernetes.Kompose` it does not isolate the instances. Patch Removing the `inter-ns` NetworkPolicy patches the vulnerability. If updates are not possible in production environments, we recommend to manually delete it and update as soon as possible. Workaround Given your context, delete the failing network policy that should be prefixed by `inter-ns-` in the target namespace. You can use the following to delete all matching network policy. If unsure of the outcome, please do it manually. ```bash for ns in $(kubectl get ns -o jsonpath='{.items[*].metadata.name}' | tr ' ' '\n' | grep '^cm-target-'); do kubectl -n "$ns" get networkpolicy -o name \ | grep '^networkpolicy.networking.k8s.io/inter-ns-' \ | xargs -r kubectl -n "$ns" delete done ```