fix(deps): update module github.com/external-secrets/external-secrets to v0.10.2 [security] #522
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.9.11
->v0.10.2
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
GitHub Vulnerability Alerts
CVE-2024-45041
Details
The external-secrets has a deployment called default-external-secrets-cert-controller, which is bound with a same-name ClusterRole. This ClusterRole has "get/list" verbs of secrets resources(https://github.com/external-secrets/external-secrets/blob/main/deploy/charts/external-secrets/templates/cert-controller-rbac.yaml#L49). It also has path/update verb of validatingwebhookconfigurations resources(https://github.com/external-secrets/external-secrets/blob/main/deploy/charts/external-secrets/templates/cert-controller-rbac.yaml#L27). As a result, if a malicious user can access the worker node which has this deployment. he/she can:
For the "get/list secrets" permission, he/she can abuse the SA token of this deployment to retrieve or get ALL secrets in the whole cluster, including the cluster-admin secret if created. After that, he/she can abuse the cluster-admin secret to do whatever he/she likes to the whole cluster, resulting in a cluster-level privilege escalation.
For the patch/update verb of validatingwebhookconfigurations, the malicious user can abuse these permissions to get sensitive data or lanuch DoS attacks:
For the privilege escalation attack, by updating/patching a Webhook to make it listen to Secret update operations, the attacker can capture and log all data from requests attempting to update Secrets. More specifically, when a Secret is updated, this Webhook sends the request data to the logging-service, which can then log the content of the Secret. This way, an attacker could indirectly gain access to the full contents of the Secret.
For the DoS attack, by updating/patching a Webhook, and making it deny all Pod create and update requests, the attacker can prevent any new Pods from being created or existing Pods from being updated, resulting in a Denial of Service (DoS) attack.
PoC
Please see the "Details" section
Impact
Privilege escalation
Release Notes
external-secrets/external-secrets (github.com/external-secrets/external-secrets)
v0.10.2
Compare Source
Image:
ghcr.io/external-secrets/external-secrets:v0.10.2
Image:
ghcr.io/external-secrets/external-secrets:v0.10.2-ubi
Image:
ghcr.io/external-secrets/external-secrets:v0.10.2-ubi-boringssl
What's Changed
Full Changelog: external-secrets/external-secrets@v0.10.1...v0.10.2
v0.10.1
Compare Source
Image:
ghcr.io/external-secrets/external-secrets:v0.10.1
Image:
ghcr.io/external-secrets/external-secrets:v0.10.1-ubi
Image:
ghcr.io/external-secrets/external-secrets:v0.10.1-ubi-boringssl
What's Changed
New Contributors
Full Changelog: external-secrets/external-secrets@v0.10.0...v0.10.1
v0.10.0
Compare Source
Webhook Generator
Webhook generator labels have changed from
generators.external-secrets.io/type: webhook
toexternal-secrets.io/type: webhook
.Webhook Provider
Webhook provider now can only use secrets that are labeled with
external-secrets.io/type: webhook
. This enforces explicit setup for webhook secrets by users.Fixing the issue:
add the label for the secret used by the webhook:
Image:
ghcr.io/external-secrets/external-secrets:v0.10.0
Image:
ghcr.io/external-secrets/external-secrets:v0.10.0-ubi
Image:
ghcr.io/external-secrets/external-secrets:v0.10.0-ubi-boringssl
What's Changed
4197211
toce46866
by @dependabot in https://github.com/external-secrets/external-secrets/pull/3663namespaceRegexes
in full-cluster-secret-store.yaml by @excalq in https://github.com/external-secrets/external-secrets/pull/36818c9183f
to8c9183f
by @dependabot in https://github.com/external-secrets/external-secrets/pull/3687PushSecret
support for Pulumi ESC by @dirien in https://github.com/external-secrets/external-secrets/pull/359777726ef
to0a4eaa0
by @dependabot in https://github.com/external-secrets/external-secrets/pull/37338c9183f
to0d3653d
by @dependabot in https://github.com/external-secrets/external-secrets/pull/37326c27802
toaf9b40f
in /e2e by @dependabot in https://github.com/external-secrets/external-secrets/pull/3734b89d9c9
to0a4eaa0
in /hack/api-docs by @dependabot in https://github.com/external-secrets/external-secrets/pull/3736New Contributors
Full Changelog: external-secrets/external-secrets@v0.9.20...v0.10.0
v0.9.20
Compare Source
Image:
ghcr.io/external-secrets/external-secrets:v0.9.20
Image:
ghcr.io/external-secrets/external-secrets:v0.9.20-ubi
Image:
ghcr.io/external-secrets/external-secrets:v0.9.20-ubi-boringssl
What's Changed
9e458f4
to5f1cd34
by @dependabot in https://github.com/external-secrets/external-secrets/pull/3568aec4784
to9678844
in /e2e by @dependabot in https://github.com/external-secrets/external-secrets/pull/35939bdd569
to6522f0c
by @dependabot in https://github.com/external-secrets/external-secrets/pull/359477726ef
tob89d9c9
in /hack/api-docs by @dependabot in https://github.com/external-secrets/external-secrets/pull/36216522f0c
toace6cc3
by @dependabot in https://github.com/external-secrets/external-secrets/pull/3620New Contributors
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.