Technical impact
A secret’s kubeconfig data is parsed by the console‑proxy’s RemoteConfigResolver without sanitizing the resulting configuration, allowing an attacker who can create or alter a Secret labeled osac.openshift.io/remote-cluster-kubeconfig: "true" to supply an exec credential plugin. The plugin is executed under the pod’s service account, giving the attacker arbitrary code execution within the operator pod. Additionally, the attacker can set the server field in the kubeconfig, which causes the proxy to issue outgoing HTTP requests to that address, creating a server‑side request forgery condition that can reach internal or external networks.
Affected Systems
The OSAC operator (osac‑project:osac‑operator) in revision 8220502, which provides a console‑proxy component for Kubernetes environments, is affected. The vulnerability manifests when the proxy’s RoleBinding grants read access to Secret objects with the proper label; the vulnerable mode is auto or remote cluster mode, whereas the local mode does not process kubeconfig secrets and therefore is not impacted.
Risk and Exploitability
The CVSS score of 8.6 reflects high impact, while the EPSS score is not available, indicating no measured exploitation data yet. The vulnerability is not listed in CISA’s KEV catalog. Exploitation requires cluster‑level permissions to create or modify secrets with the specific label in a namespace where the console‑proxy can read them. After satisfying this prerequisite, the attacker can trigger the exec plugin to run arbitrary code as the pod’s service account and can also direct the proxy to perform SSRF against any reachable address.
Github GHSA