Skip to content
Noroxi
NVD / CVE Program· CNA kubernetes

CVE-2024-3177: Bypassing mountable secrets policy imposed by the ServiceAccount admission plugin

Noroxi assessment

Priority: Monitor (action score 11/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 2.2% (FIRST EPSS); higher than 82.7% of all records.
  • Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: kubernetes (Debian:12) 1.20.5+really1.20.2-1; k8s.io/kubernetes (Go) 1.28.9, 1.29.4, 1.27.13; kubernetes1.23 (openSUSE:Leap 15.5) 1.23.17-150500.3.12.1.

Low priority for now. Upgrade to kubernetes (Debian:12) 1.20.5+really1.20.2-1; k8s.io/kubernetes (Go) 1.28.9, 1.29.4, 1.27.13; kubernetes1.23 (openSUSE:Leap 15.5) 1.23.17-150500.3.12.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

A security issue was discovered in Kubernetes where users may be able to launch containers that bypass the mountable secrets policy enforced by the ServiceAccount admission plugin when using containers, init containers, and ephemeral containers with the envFrom field populated. 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 containers, init containers, and ephemeral containers with the envFrom field populated.

LowCVSS 2.7 · v3.1—Proof of concept Fix available
Published
Apr 22, 2024
Updated
Jun 17, 2026
EPSS
2.2% · 82th percentile

Report tools

JSON

Action score

11

Monitor

Low priority for now.

CVSS
10 / 40 · 2.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · kubernetes
2.7
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-3177

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
kuberneteskubernetes

Using kubernetes? Add it to your stack and be the first to know about CVEs like this one. (Kubernetes)

Watch new CVEs for kubernetes

When you'll hear from us

  • when a new CVE affecting this product is published
  • when a record in your stack enters KEV or gets exploit code

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Versions reported by the vendor

Affected version ranges reported by the assigning authority (kubernetes). Independent of NVD's CPE analysis and usually ahead of it.

  • Kubernetes Kubernetes

    • v1.28.0 - v1.28.8, v1.29.0 - v1.29.3affected
    • up to and including 1.27.12affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12kubernetesbefore 1.20.5+really1.20.2-11.20.5+really1.20.2-1
Gok8s.io/kubernetesfrom 1.28.0 · before 1.28.91.28.9
Gok8s.io/kubernetesfrom 1.29.0 · before 1.29.41.29.4
Gok8s.io/kubernetesbefore 1.27.131.27.13
openSUSE:Leap 15.5kubernetes1.23before 1.23.17-150500.3.12.11.23.17-150500.3.12.1
openSUSE:Leap 15.5kubernetes1.24before 1.24.17-150500.3.16.11.24.17-150500.3.16.1
Red Hat:openshift:4.14::el8openshiftbefore 0:4.14.0-202404231437.p0.g401bb48.assembly.stream.el80:4.14.0-202404231437.p0.g401bb48.assembly.stream.el8
Red Hat:openshift:4.14::el8openshift-hyperkubebefore 0:4.14.0-202404231437.p0.g401bb48.assembly.stream.el80:4.14.0-202404231437.p0.g401bb48.assembly.stream.el8
Red Hat:openshift:4.14::el8skopeobefore 2:1.11.3-0.1.rhaos4.14.el82:1.11.3-0.1.rhaos4.14.el8
Red Hat:openshift:4.14::el8skopeo-debuginfobefore 2:1.11.3-0.1.rhaos4.14.el82:1.11.3-0.1.rhaos4.14.el8
Red Hat:openshift:4.14::el8skopeo-debugsourcebefore 2:1.11.3-0.1.rhaos4.14.el82:1.11.3-0.1.rhaos4.14.el8
Red Hat:openshift:4.14::el8skopeo-testsbefore 2:1.11.3-0.1.rhaos4.14.el82:1.11.3-0.1.rhaos4.14.el8
Red Hat:openshift:4.14::el9openshiftbefore 0:4.14.0-202404231437.p0.g401bb48.assembly.stream.el90:4.14.0-202404231437.p0.g401bb48.assembly.stream.el9
Red Hat:openshift:4.14::el9openshift-hyperkubebefore 0:4.14.0-202404231437.p0.g401bb48.assembly.stream.el90:4.14.0-202404231437.p0.g401bb48.assembly.stream.el9
Red Hat:openshift:4.14::el9skopeobefore 2:1.11.3-0.1.rhaos4.14.el92:1.11.3-0.1.rhaos4.14.el9
Red Hat:openshift:4.14::el9skopeo-debuginfobefore 2:1.11.3-0.1.rhaos4.14.el92:1.11.3-0.1.rhaos4.14.el9
Red Hat:openshift:4.14::el9skopeo-debugsourcebefore 2:1.11.3-0.1.rhaos4.14.el92:1.11.3-0.1.rhaos4.14.el9
Red Hat:openshift:4.14::el9skopeo-testsbefore 2:1.11.3-0.1.rhaos4.14.el92:1.11.3-0.1.rhaos4.14.el9
Red Hat:openshift:4.16::el9microshiftbefore 0:4.16.0-202406260523.p0.gc5a37df.assembly.4.16.0.el90:4.16.0-202406260523.p0.gc5a37df.assembly.4.16.0.el9
Red Hat:openshift:4.16::el9microshift-greenbootbefore 0:4.16.0-202406260523.p0.gc5a37df.assembly.4.16.0.el90:4.16.0-202406260523.p0.gc5a37df.assembly.4.16.0.el9
Red Hat:openshift:4.16::el9microshift-multusbefore 0:4.16.0-202406260523.p0.gc5a37df.assembly.4.16.0.el90:4.16.0-202406260523.p0.gc5a37df.assembly.4.16.0.el9
Red Hat:openshift:4.16::el9microshift-multus-release-infobefore 0:4.16.0-202406260523.p0.gc5a37df.assembly.4.16.0.el90:4.16.0-202406260523.p0.gc5a37df.assembly.4.16.0.el9
Red Hat:openshift:4.16::el9microshift-networkingbefore 0:4.16.0-202406260523.p0.gc5a37df.assembly.4.16.0.el90:4.16.0-202406260523.p0.gc5a37df.assembly.4.16.0.el9
Red Hat:openshift:4.16::el9microshift-olmbefore 0:4.16.0-202406260523.p0.gc5a37df.assembly.4.16.0.el90:4.16.0-202406260523.p0.gc5a37df.assembly.4.16.0.el9

+8

Other highest-scoring records for the same primary product.

  • CVE-2018-1002105In all Kubernetes versions prior to v1.10.11, v1.11.5, and v1.12.3, incorrect handling of error responses to proxied upgrade requests in the
    65This week
  • CVE-2019-11248Kubernetes kubelet exposes /debug/pprof info on healthz port
    55Plan
  • CVE-2017-1002101In Kubernetes versions 1.3.x, 1.4.x, 1.5.x, 1.6.x and prior to versions 1.7.14, 1.8.9 and 1.9.4 containers using subpath volume mounts with
    42Plan

Published before and after this one in the same product

  • ← EarlierCVE-2023-3955Oct 31, 2023 · Kubernetes - Windows nodes - Insufficient input sanitization leads to privilege escalation
    36Monitor
  • ← EarlierCVE-2023-5528Nov 14, 2023 · Kubernetes - Windows nodes - Insufficient input sanitization in in-tree storage plugin leads to privilege escalation
    36Monitor
  • Later →CVE-2024-5321Jul 18, 2024 · Incorrect permissions on Windows containers logs
    24Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:kubernetes1.20.5+really1.20.2-1 · Debian:12Package registry (OSV)
Go:k8s.io/kubernetes1.27.13Package registry (OSV)
Go:k8s.io/kubernetes1.28.9Package registry (OSV)
Go:k8s.io/kubernetes1.29.4Package registry (OSV)
opensuse:kubernetes1.231.23.17-150500.3.12.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kubernetes1.241.24.17-150500.3.16.1 · openSUSE:Leap 15.5Package registry (OSV)
red hat:microshift0:4.16.0-202406260523.p0.gc5a37df.assembly.4.16.0.el9 · Red Hat:openshift:4.16::el9Package registry (OSV)
red hat:microshift-greenboot0:4.16.0-202406260523.p0.gc5a37df.assembly.4.16.0.el9 · Red Hat:openshift:4.16::el9Package registry (OSV)
red hat:microshift-multus0:4.16.0-202406260523.p0.gc5a37df.assembly.4.16.0.el9 · Red Hat:openshift:4.16::el9Package registry (OSV)
red hat:microshift-multus-release-info0:4.16.0-202406260523.p0.gc5a37df.assembly.4.16.0.el9 · Red Hat:openshift:4.16::el9Package registry (OSV)
red hat:microshift-networking0:4.16.0-202406260523.p0.gc5a37df.assembly.4.16.0.el9 · Red Hat:openshift:4.16::el9Package registry (OSV)
red hat:microshift-olm0:4.16.0-202406260523.p0.gc5a37df.assembly.4.16.0.el9 · Red Hat:openshift:4.16::el9Package registry (OSV)
red hat:microshift-olm-release-info0:4.16.0-202406260523.p0.gc5a37df.assembly.4.16.0.el9 · Red Hat:openshift:4.16::el9Package registry (OSV)
red hat:microshift-release-info0:4.16.0-202406260523.p0.gc5a37df.assembly.4.16.0.el9 · Red Hat:openshift:4.16::el9Package registry (OSV)
red hat:microshift-selinux0:4.16.0-202406260523.p0.gc5a37df.assembly.4.16.0.el9 · Red Hat:openshift:4.16::el9Package registry (OSV)
red hat:openshift0:4.14.0-202404231437.p0.g401bb48.assembly.stream.el8 · Red Hat:openshift:4.14::el8Package registry (OSV)
red hat:openshift-hyperkube0:4.14.0-202404231437.p0.g401bb48.assembly.stream.el8 · Red Hat:openshift:4.14::el8Package registry (OSV)
red hat:skopeo2:1.11.3-0.1.rhaos4.14.el8 · Red Hat:openshift:4.14::el8Package registry (OSV)
suse:kubernetes1.231.23.17-150500.3.12.1 · SUSE:Linux Enterprise Module for Containers 15 SP5Package registry (OSV)
suse:kubernetes1.241.24.17-150500.3.16.1 · SUSE:Linux Enterprise Module for Containers 15 SP5Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02024-09-05

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+135 d
  3. TodayNov 2, 2026+924 d

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2023-3676174 days apartKubernetes - Windows nodes - Insufficient input sanitization leads to privilege escalation
    39Monitor
  • CVE-2023-5528160 days apartKubernetes - Windows nodes - Insufficient input sanitization in in-tree storage plugin leads to privilege escalation
    36Monitor
  • CVE-2023-3955174 days apartKubernetes - Windows nodes - Insufficient input sanitization leads to privilege escalation
    36Monitor
  • CVE-2022-3294418 days apartNode address isn't always verified when proxying
    35Monitor
  • CVE-2023-2728294 days apartBypassing enforce mountable secrets policy imposed by the ServiceAccount admission plugin
    27Monitor
  • CVE-2023-2727294 days apartBypassing policies imposed by the ImagePolicyWebhook admission plugin
    26Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • Administrator privileges are required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N

nvd-secondary

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records