Duplicate Advisory: k8s.io/kube-state-metrics Exposure of Sensitive Information
Red Hat kube-state-metrics
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/kubernetes/kube-state-metrics Go |
|
|
| k8s.io/kube-state-metrics Go |
|
|
Red Hat kube-state-metrics
| Product | Affected | Fixed in |
|---|---|---|
| github.com/kubernetes/kube-state-metrics Go |
|
|
| k8s.io/kube-state-metrics Go |
|
|
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.
From the CVE record · redhat
In kube-state-metrics v1.7.0 and v1.7.1, an experimental annotation-metrics feature combined with default kubectl behavior can put entire Secret contents into metric labels. Someone who can view those metrics could see the secrets; the input does not specify whether authentication or user interaction is required.
Anyone running Red Hat kube-state-metrics or the Go packages github.com/kubernetes/kube-state-metrics or k8s.io/kube-state-metrics at versions >=1.7.0 and <1.7.2 should check.