Skip to content

Duplicate Advisory: k8s.io/kube-state-metrics Exposure of Sensitive Information

Moderate severity GitHub Reviewed Published May 18, 2021 to the GitHub Advisory Database • Updated Jan 23, 2024
Withdrawn This advisory was withdrawn on Jan 23, 2024

Package

gomod github.com/kubernetes/kube-state-metrics (Go)

Affected versions

>= 1.7.0, < 1.7.2

Patched versions

1.7.2
gomod k8s.io/kube-state-metrics (Go)
>= 1.7.0, < 1.7.2
1.7.2

Description

Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-c92w-72c5-9x59. This link is maintained to preserve external references.

Original Description

A security issue was discovered in kube-state-metrics 1.7.x before 1.7.2. An experimental feature was added to v1.7.0 and v1.7.1 that enabled annotations to be exposed as metrics. By default, 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.

References

Reviewed May 17, 2021
Published to the GitHub Advisory Database May 18, 2021
Last updated Jan 23, 2024
Withdrawn Jan 23, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.241%
(63rd percentile)

Weaknesses

CVE ID

CVE-2019-17110

GHSA ID

GHSA-2v6x-frw8-7r7f

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.