kube-state-metrics: annotations exposed as metrics in combination with `kubectl` can allow for exposure of secrets
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Red Hat | kube-state-metrics | affected |
|
Configuration 1 [-]
| AND |
|
Configuration 2 [-]
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2022-3542 | A security issue was discovered in the kube-state-metrics versions v1.7.0 and v1.7.1. An experimental feature was added to the v1.7.0 release that enabled annotations to be exposed as metrics. By default, the kube-state-metrics metrics only expose metadata about Secrets. However, a combination of the default `kubectl` behavior and this new feature can cause the entire secret content to end up in metric labels thus inadvertently exposing the secret content in metrics. This feature has been reverted and released as the v1.7.2 release. If you are running the v1.7.0 or v1.7.1 release, please upgrade to the v1.7.2 release as soon as possible. |
Github GHSA |
GHSA-c92w-72c5-9x59 | kube-state-metrics may expose secret content in metrics |
No CVSS v4.0
This CVE is not in the KEV list.
Exploit prediction score: 1.8% (1.780% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.