External Secrets Operator: Namespace Isolation Bypass in CAProvider ConfigMap Resolution for SecretStore
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| external-secrets | external-secrets | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| External-secrets | External-secrets |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-wv26-88m5-6h59 | External Secrets Operator has Namespace Isolation Bypass in CAProvider ConfigMap Resolution for SecretStore |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.240% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
External-secrets
External-secrets external-secrets |
|
| Vendors & Products |
External-secrets
External-secrets external-secrets |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | External Secrets Operator reads information from a third-party service and automatically injects the values as Kubernetes Secrets. Prior to 2.4.0, Namespaced SecretStore resources that used CAProvider with type ConfigMap could resolve CA material from another namespace when caProvider.namespace was set. This bypassed the namespace boundary enforced for SecretStore-backed references in providers that rely on the shared runtime CA resolver. This vulnerability is fixed in 2.4.0. | |
| Title | External Secrets Operator: Namespace Isolation Bypass in CAProvider ConfigMap Resolution for SecretStore | |
| Weaknesses | CWE-285 CWE-668 |
|
| References |
| |
| Metrics |
cvssV4_0
|