CyberRota Analysis
AI-GeneratedKubernetes installations using Omni versions 1.3.0 to 1.6.6 and 1.7.3 are vulnerable due to improper access controls that allow authenticated users with the Reader role to access sensitive ImportedClusterSecrets, which include CA private keys and service-account keys. This exposure can lead to unauthorized control over the imported cluster, enabling potential compromise of workloads and sensitive data. Organizations utilizing these versions should prioritize upgrading to the patched versions 1.6.6 or 1.7.3 to mitigate the risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Omni manages Kubernetes on bare metal, virtual machines, or in a cloud. From 1.3.0 until 1.6.6 and 1.7.3, importing a standalone Talos cluster creates an ImportedClusterSecrets resource containing the cluster's complete CA secrets bundle. The access rules in internal/backend/runtime/omni/state_access.go allow an authenticated user with the Reader role to retrieve the resource through ResourceService if the importing actor has not rotated those secrets, exposing Kubernetes, Talos, and etcd CA private keys plus the service-account key. The Kubernetes CA private key permits certificate signing for privileged identities such as system:masters and provides control of the imported cluster outside Omni's authorization boundary, including its workloads, credentials, and secrets. This issue is fixed in versions 1.6.6 and 1.7.3.