Skip to content

Kubernetes mountable secrets policy bypass

Moderate severity GitHub Reviewed Published Jul 3, 2023 to the GitHub Advisory Database • Updated Feb 13, 2025

Package

gomod k8s.io/kubernetes (Go)

Affected versions

>= 1.27.0, < 1.27.3
>= 1.26.0, < 1.26.6
>= 1.25.0, < 1.25.11
< 1.24.15

Patched versions

1.27.3
1.26.6
1.25.11
1.24.15

Description

Users may be able to launch containers that bypass the mountable secrets policy enforced by the ServiceAccount admission plugin when using ephemeral containers. The policy ensures pods running with a service account may only reference secrets specified in the service account’s secrets field. Kubernetes clusters are only affected if the ServiceAccount admission plugin and the kubernetes.io/enforce-mountable-secrets annotation are used together with ephemeral containers.

References

Published by the National Vulnerability Database Jul 3, 2023
Published to the GitHub Advisory Database Jul 3, 2023
Reviewed Jul 6, 2023
Last updated Feb 13, 2025

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
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:H/UI:N/S:U/C:H/I:H/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(54th percentile)

Weaknesses

CVE ID

CVE-2023-2728

GHSA ID

GHSA-cgcv-5272-97pr

Source code

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