CVE-2019-17110: Exposure of Sensitive Information in kube-state-metrics
Summary
CVE-2019-10223: Duplicate Advisory: k8s.io/kube-state-metrics Exposure of Sensitive Information. Affects github.com/kubernetes/kube-state-metrics versions >= 1.7.0, < 1.7.2. Fixed in 1.7.2. How to fix ↓
Also tracked for
The same CVE-2019-10223 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
kube-state-metrics is a Go package that provides metrics about the state of various Kubernetes objects. It exposes metadata about Secrets by default. However, an experimental feature added in versions 1.7.0 and 1.7.1 allowed annotations to be exposed as metrics. This feature, when combined with the default behavior of kubectl, can inadvertently expose the entire secret content in metric labels.
Vulnerability Detail
The vulnerability (CVE-2019-17110) in kube-state-metrics versions 1.7.x before 1.7.2 allows an unauthorized actor to access sensitive information. By default, kube-state-metrics only exposes metadata about Secrets. However, due to a combination of default kubectl behavior and the experimental feature, the secret content can end up in metric labels, unintentionally exposing it. This can lead to unauthorized access to sensitive information contained within the exposed secrets.
How To Fix
Minimum fixed version
1.7.2
This is the first release that contains the fix.
go get github.com/kubernetes/kube-state-metrics@v1.7.2Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There is no specific workaround provided for this vulnerability. Upgrading to the fixed version is the recommended solution.
Conclusion
In conclusion, the vulnerability (CVE-2019-17110) in kube-state-metrics versions 1.7.x before 1.7.2 allows unauthorized access to sensitive information. Upgrading to version 1.7.2 or later is necessary to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for github.com/kubernetes/kube-state-metrics →
FAQ
kube-state-metrics is a Go package that provides metrics about the state of various Kubernetes objects.
This vulnerability can lead to the exposure of sensitive information contained within Kubernetes secrets.
Versions 1.7.0 and 1.7.1 of kube-state-metrics are affected by this vulnerability.
To fix this vulnerability, upgrade kube-state-metrics to version 1.7.2 or later.
No, there is no specific workaround provided. Upgrading to the fixed version is the recommended solution.
