Windows kube-proxy LoadBalancer contention
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Kubernetes | Kubernetes | unaffected |
|
Configuration 1 [-]
| AND |
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat OpenShift Container Platform 4.7 | |||
| openshift4-wincw/windows-machine-config-operator-bundle:v2.0.1-8 | cpe:/a:redhat:openshift:4.7::el8 | RHSA-2021:2130 | 2021-06-23T00:00:00Z |
| openshift4-wincw/windows-machine-config-rhel8-operator:2.0.1-6 | cpe:/a:redhat:openshift:4.7::el8 | RHSA-2021:2130 | 2021-06-23T00:00:00Z |
No data available yet.
Vendor Solution
This issue has been fixed in the following versions: * v1.21.0 * v1.20.6 * v1.19.10 * v1.18.18
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2023-2624 | Kube-proxy on Windows can unintentionally forward traffic to local processes listening on the same port (“spec.ports[*].port”) as a LoadBalancer Service when the LoadBalancer controller does not set the “status.loadBalancer.ingress[].ip” field. Clusters where the LoadBalancer controller sets the “status.loadBalancer.ingress[].ip” field are unaffected. |
Github GHSA |
GHSA-35c7-w35f-xwgh | Kube-proxy may unintentionally forward traffic |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.915% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-114 | |
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Kube-proxy on Windows can unintentionally forward traffic to local processes listening on the same port (“spec.ports[*].port”) as a LoadBalancer Service when the LoadBalancer controller does not set the “status.loadBalancer.ingress[].ip” field. Clusters where the LoadBalancer controller sets the “status.loadBalancer.ingress[].ip” field are unaffected. | Kube-proxy on Windows can unintentionally forward traffic to local processes listening on the same port (“spec.ports[*].port”) as a LoadBalancer Service when the LoadBalancer controller does not set the “status.loadBalancer.ingress[].ip” field. Clusters where the LoadBalancer controller sets the “status.loadBalancer.ingress[].ip” field are unaffected. |