Kubernetes Secret access exceeds tenant permissions
A restricted cluster principal can read a canary Secret outside its intended resource boundary.
Candidate CWE: CWE-732
Test hypothesis#
Query permission for the named Secret using the actual low-privilege context; if a read is allowed by the test scope, retrieve only the administrator-created canary and compare a correctly restricted identity.
Evidence required#
Context identity, namespace/name, effective RBAC grants, authorization result and only the synthetic marker. Avoid Secret lists and real credential content.
Rule out false positives#
Intended cluster administration, intentionally shared namespace secrets, or a permission query without the relevant complete resource/subresource context.
Playbook and command references#
- Container and Kubernetes isolation — Test RBAC, workload identity, admission, networking and host exposure as separate enforcement layers.
Find the associated command snippets
Referenced by these target playbooks#
Report checklist#
- Capture the affected version, configuration, identities, and object ownership.
- Preserve a valid baseline and a negative control.
- Reproduce the forbidden data access, action, or state change on controlled fixtures.
- Explain the intended security rule and why the observed behavior violates it.
- State prerequisites, uncertainty, cleanup, and the smallest demonstrated impact.
Conditional ATT&CK mapping#
No direct ATT&CK mapping selected. Record the weakness and demonstrated impact without forcing an adversary-behavior classification. See the mapping guide.