github.com/ctfer-io/monitoring Vulnerable to Improper Access Control

Impact

Due to a mis-written NetworkPolicy, a malicious actor can pivot from a component to any other namespace. This breaks the security-by-default property expected as part of the deployment program, leading to a potential lateral movement.

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 monitoring namespace. You can use the following to delete all matching network policy. If unsure of the outcome, please do it manually.

for ns in $(kubectl get ns -o jsonpath='{.items[*].metadata.name}' | tr ' ' '\n' | grep '^monitoring-'); do
  kubectl -n "$ns" get networkpolicy -o name \
  | grep '^networkpolicy.networking.k8s.io/inter-ns-' \
  | xargs -r kubectl -n "$ns" delete
done