I just found that the Deployment emissary-ingress in the charts has both list and get verbs for the secrets resource (rbac.yaml#L13). However, after reading the source code of emissary, I didn't find any Kubernetes API usages that require list secrets permissions. If malicious users gain control of a Kubernetes node running a emissary-ingress pod, they can list all the names of the secrets, and with the name, they can get the details of all the secrets objects (since this is declared in a ClusterRole).Therefore, for security reasons, I suggest checking this permission to determine if it is truly unnecessary. If it is, the issue should be fixed by removing the unnecessary permission or or other feasible methods.
Hi community!
I just found that the Deployment emissary-ingress in the charts has both
listandgetverbs for thesecretsresource (rbac.yaml#L13). However, after reading the source code of emissary, I didn't find any Kubernetes API usages that requirelistsecrets permissions. If malicious users gain control of a Kubernetes node running aemissary-ingresspod, they can list all the names of the secrets, and with the name, they can get the details of all the secrets objects (since this is declared in a ClusterRole).Therefore, for security reasons, I suggest checking this permission to determine if it is truly unnecessary. If it is, the issue should be fixed by removing the unnecessary permission or or other feasible methods.To Reproduce Use helm chart with default values.