Bug 1740431 (CVE-2019-10223)

Summary: CVE-2019-10223 kube-state-metrics: annotations exposed as metrics in combination with `kubectl` can allow for exposure of secrets
Product: [Other] Security Response Reporter: Sam Fowler <sfowler>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: ahardin, alegrand, anpicker, bleanhar, bmontgom, ccoleman, dedgar, eparis, erooth, jburrell, jgoulding, jokerman, kakkoyun, lcosic, mchappel, mloibl, mrehak, nstielau, pkrupa, sponnaga, surbania
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: kube-state-metrics 1.7.2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-13 02:47:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1739957, 1759119    

Description Sam Fowler 2019-08-13 00:53:07 UTC
A security issue was discovered in the v1.7.0 and v1.7.1 versions of kube-state-metrics. 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.

Comment 1 Sam Fowler 2019-08-13 00:54:31 UTC
External References:

https://www.openwall.com/lists/oss-security/2019/08/09/1

Comment 3 Sam Fowler 2019-12-01 23:41:32 UTC
*** Bug 1759118 has been marked as a duplicate of this bug. ***