CVSS 3.1
5.9 mediumCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:NMedium (5.9) in kubernetes kubelet. EPSS 1.4% estimated probability of exploitation activity in the next 30 days. Fixed in k8s.io/kubernetes 1.29.13, 1.30.9, 1.31.5.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:Nk8s.io/kubernetes (Go): fixed in 1.29.13, 1.30.9, 1.31.5, 1.32.1Explain CVE-2024-9042 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-9042?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-9042?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-9042 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Kubernetes Kubelet | <=v1.29.12 |
| Kubernetes Kubelet | from v1.30 through v1.30.8 |
| Kubernetes Kubelet | from v1.31 through v1.31.4 |
| Kubernetes Kubelet | from v1.32 through v1.32.0 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-vv39-3w5q-974q | Go | k8s.io/kubernetes | <1.29.13 | 1.29.13 |
| GHSA-vv39-3w5q-974q | Go | k8s.io/kubernetes | >=1.30.0-alpha.0 <1.30.9 | 1.30.9 |
| GHSA-vv39-3w5q-974q | Go | k8s.io/kubernetes | >=1.31.0-alpha.0 <1.31.5 | 1.31.5 |
| GHSA-vv39-3w5q-974q | Go | k8s.io/kubernetes | >=1.32.0-alpha.0 <1.32.1 | 1.32.1 |
| GO-2025-3522 | Go | k8s.io/kubernetes | <1.29.13 >=1.30.0-alpha.0 <1.30.9 >=1.31.0-alpha.0 <1.31.5 >=1.32.0-alpha.0 <1.32.1 | 1.29.13, 1.30.9, 1.31.5, 1.32.1 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| openSUSE | Tumbleweed | govulncheck-vulndb | 0.0.20250327T184518-1.1 | openSUSE-SU-2025:14937-1 |
From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: openSUSE.
Red Hat rates this Moderate.
This CVE affects only Windows worker nodes. To detect whether this vulnerability has been exploited, you can examine your cluster's audit logs to search for node 'logs' queries with suspicious inputs.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| OpenShift Windows Machine Config Operator 10.16 | openshift4-wincw/windows-machine-config-rhel9-operator:v10.16.2-1749241361 | Fixed 2025-06-16 | RHSA-2025:9136 |
| OpenShift Windows Machine Config Operator 10.17 | openshift4-wincw/windows-machine-config-rhel9-operator:9.6-1748967421 | Fixed 2025-06-09 | RHSA-2025:8704 |
| Red Hat OpenShift Container Platform 4 | openshift | Fix deferred |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2024-9042.
Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).