Description
External Secrets Operator reads information from a third-party service and automatically injects the values as Kubernetes Secrets. Starting in version 0.20.2 and prior to version 1.2.0, the `getSecretKey` template function, while introduced for senhasegura Devops Secrets Management (DSM) provider, has the ability to fetch secrets cross-namespaces with the roleBinding of the external-secrets controller, bypassing our security mechanisms. This function was completely removed in version 1.2.0, as everything done with that templating function can be done in a different way while respecting External Secrets Operator's safeguards As a workaround, use a policy engine such as Kubernetes, Kyverno, Kubewarden, or OPA to prevent the usage of `getSecretKey` in any ExternalSecret resource.
Problem types
CWE-863: Incorrect Authorization
Product status
References
github.com/...ecrets/security/advisories/GHSA-77v3-r3jw-j2v2
github.com/external-secrets/external-secrets/issues/5690
github.com/external-secrets/external-secrets/pull/3895
github.com/...ommit/17d3e22b8d3fbe339faf8515a95ec06ec92b1feb
github.com/...l-secrets/external-secrets/releases/tag/v1.2.0