KubeVirt Affected by an Authentication Bypass in Kubernetes Aggregation Layer
kubevirt
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| kubevirt.io/kubevirt Go |
|
|
kubevirt
| Product | Affected | Fixed in |
|---|---|---|
| kubevirt.io/kubevirt Go |
|
|
1.6.11.7.0-rc.01.6.0-beta.0.0.20250730135146-231dc69723f3KubeVirt is a virtual machine management add-on for Kubernetes. Versions 1.5.3 and below, and 1.6.0 contained a flawed implementation of the Kubernetes aggregation layer's authentication flow which could enable bypass of RBAC controls. It was discovered that the virt-api component fails to correctly authenticate the client when receiving API requests over mTLS. In particular, it fails to validate the CN (Common Name) field in the received client TLS certificates against the set of allowed values defined in the extension-apiserver-authentication configmap. Failre to validate certain fields in the client TLS certificate may allow an attacker to bypass existing RBAC controls by directly communicating with the aggregated API server, impersonating the Kubernetes API server and its aggregator component. This issue is fixed in versions 1.5.3 and 1.6.1.
From the CVE record · GitHub_M
KubeVirt’s virt-api does not validate the client certificate’s Common Name against allowed values when handling API requests over mTLS. An attacker who can communicate directly with the aggregated API server using a client certificate may impersonate the Kubernetes API server’s aggregator component and bypass RBAC controls. No user interaction is described.
Teams running the Go package kubevirt.io/kubevirt should check installations earlier than 1.5.3 and affected 1.6 and 1.7 pre-release versions.