Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
CVE-2024-7598
Summary
A security issue was discovered in Kubernetes versions from 1.30.x through v1.30.11, v1.31.x through v1.31.6, v1.32.x through v1.32.2 and v1.33.0-alpha.0 through v1.33.0-alpha.2.0.x 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.
- HIGH
- ADJACENT_NETWORK
- NONE
- UNCHANGED
- NONE
- NONE
- LOW
- NONE
CWE-362 - Race Condition
A race condition occurs in a shared memory program when two threads/processes access the same shared memory data, and at least one thread executes a write operation. This vulnerability manipulates the time to check vs. time to use (TOC/TOU) gap between the threads in the critical section to cause disorientation in the shared data. The impact can vary from compromising the confidentiality of the system to causing the system to crash or to execute arbitrary code.
References
Advisory Timeline
- Published
