CVE-2023-3676: Insufficient input sanitization on Windows nodes leads to privilege escalation #119339
Labels
area/kubelet
area/security
committee/security-response
Denotes an issue or PR intended to be handled by the product security committee.
kind/bug
Categorizes issue or PR as related to a bug.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
official-cve-feed
Issues or PRs related to CVEs officially announced by Security Response Committee (SRC)
sig/windows
Categorizes an issue or PR as relevant to SIG Windows.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
CVSS Rating: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - HIGH (8.8)
A security issue was discovered in Kubernetes where a user that can create pods on Windows nodes may be able to escalate to admin privileges on those nodes. Kubernetes clusters are only affected if they include Windows nodes.
Am I vulnerable?
Any kubernetes environment with Windows nodes is impacted. Run
kubectl get nodes -l kubernetes.io/os=windows
to see if any Windows nodes are in use.Affected Versions
How do I mitigate this vulnerability?
The provided patch fully mitigates the vulnerability and has no known side effects. Full mitigation for this class of issues requires patches applied for CVE-2023-3676, CVE-2023-3955, and CVE-2023-3893.
Outside of applying the provided patch, there are no known mitigations to this vulnerability.
Fixed Versions
To upgrade, refer to the documentation:
https://kubernetes.io/docs/tasks/administer-cluster/cluster-upgrade/
Detection
Kubernetes audit logs can be used to detect if this vulnerability is being exploited. Pod create events with embedded powershell commands are a strong indication of exploitation. Config maps and secrets that contain embedded powershell commands and are mounted into pods are also a strong indication of exploitation.
If you find evidence that this vulnerability has been exploited, please contact [email protected]
Acknowledgements
This vulnerability was reported by Tomer Peled @tomerpeled92
The issue was fixed and coordinated by the fix team:
James Sturtevant @jsturtevant
Mark Rossetti @marosset
Andy Zhang @andyzhangx
Justin Terry @jterry75
Kulwant Singh @KlwntSingh
Micah Hausler @micahhausler
Rita Zhang @ritazh
and release managers:
Jeremy Rickard @jeremyrickard
/triage accepted
/lifecycle frozen
/area security
/kind bug
/committee security-response
The text was updated successfully, but these errors were encountered: