CVE-2024-7598: Network restriction bypass via race condition during namespace termination
A security issue was discovered in Kubernetes where a malicious or compromised pod could bypass network restrictions enforced by network policies during namespace deletion. The order in which objects are deleted during namespace termination is not defined, and it is possible for network policies to be deleted before the pods that they protect. This can lead to a brief period in which the pods are running, but network policies that should apply to connections to and from the pods are not enforced.
Other sources
Network restriction bypass via race condition during namespace termination
— Microsoft
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.30.10-26 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.30.10-27
Event History
Frequently Asked Questions
What is the severity of CVE-2024-7598?
The severity of CVE-2024-7598 is considered to be high due to the potential for network policy bypass during namespace deletion.
How do I fix CVE-2024-7598?
To fix CVE-2024-7598, you should update Kubernetes to the latest version where this vulnerability has been addressed.
What specific component of Kubernetes is affected by CVE-2024-7598?
CVE-2024-7598 affects the network policy enforcement component in Kubernetes.
How does CVE-2024-7598 impact network policies in Kubernetes?
CVE-2024-7598 allows a malicious pod to bypass network restrictions set by network policies during the deletion of namespaces.
Is there a workaround for CVE-2024-7598 if I cannot immediately update my Kubernetes version?
While there is no official workaround, you can limit the privileges of pods in namespaces to mitigate the impact of CVE-2024-7598.