A vulnerability exists in the NodeRestriction admission controller in Kubernetes clusters where node users can delete their corresponding node object by patching themselves with an OwnerReference to a cluster-scoped resource. If the OwnerReference resource does not exist or is subsequently deleted, the given node object will be deleted via garbage collection.
Solution:
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Link | Tags |
---|---|
https://github.com/kubernetes/kubernetes/issues/133471 | issue tracking |
https://groups.google.com/g/kubernetes-security-announce/c/znSNY7XCztE | mailing list |