Node address isn't always verified when proxying
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 | affected |
|
Configuration 1 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat OpenShift Container Platform 4.12 | |||
| microshift-0:4.12.1-202301261525.p0.g3db9e81.assembly.4.12.1.el8 | cpe:/a:redhat:openshift:4.12::el8 | RHBA-2023:0452 | 2023-01-30T00:00:00Z |
No data available yet.
Vendor Workaround
Configuring an egress proxy for egress to the cluster network can mitigate this vulnerability
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2023-1049 | Users may have access to secure endpoints in the control plane network. Kubernetes clusters are only affected if an untrusted user can modify Node objects and send proxy requests to them. Kubernetes supports node proxying, which allows clients of kube-apiserver to access endpoints of a Kubelet to establish connections to Pods, retrieve container logs, and more. While Kubernetes already validates the proxying address for Nodes, a bug in kube-apiserver made it possible to bypass this validation. Bypassing this validation could allow authenticated requests destined for Nodes to to the API server's private network. |
Github GHSA |
GHSA-jh36-q97c-9928 | Kubernetes vulnerable to validation bypass |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 1.6% (1.618% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|