Skip to content

Document tested K8sPEASS permission attack paths - #377

Open
carlospolop wants to merge 8 commits into
masterfrom
codex/k8speass-risk-paths-20260907
Open

Document tested K8sPEASS permission attack paths#377
carlospolop wants to merge 8 commits into
masterfrom
codex/k8speass-risk-paths-20260907

Conversation

@carlospolop

Copy link
Copy Markdown
Collaborator

Summary

  • document K8sPEASS read-only permission enumeration and severity interpretation
  • map every active critical/high K8sPEASS permission family to a concrete attack path
  • keep controller-dependent and unverified paths at medium instead of presenting them as true positives
  • add reproduced Service/EndpointSlice, NetworkPolicy, ValidatingAdmissionPolicyBinding, ConfigMap, ClusterTrustBundle, PersistentVolume, direct binding, CSR, and non-resource debug checks

Validation

  • reproduced permission chains with dedicated identities and negative controls on disposable Minikube Kubernetes v1.37.0 profiles
  • reproduced NetworkPolicy deny/patch/restore using Calico
  • isolated nodes/proxy no-grant, get-only WebSocket exec, and create-only /run paths
  • verified authorized-but-unserved API and /logs grants are not counted as active high findings
  • MDBOOK_BOOK__LANGUAGE=en mdbook build (passes; existing unrelated warnings only)
  • git diff --check

All K8sPEASS Minikube profiles, Docker containers, generated book files, and temporary test evidence were removed after validation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant