Osac Operator
Monthly
OSAC operator's console-proxy can be induced to execute an attacker-supplied credential plugin inside its pod, yielding code execution as the osac-console-proxy service account in affected revisions such as 8220502. The issue is high severity (CVSS 8.6) and affects deployments in remote or auto VM cluster mode, with auto the default; deployments using local mode exclusively are unaffected because they do not read kubeconfig Secrets. Exploitation requires a principal able to create or modify a Secret labeled osac.openshift.io/remote-cluster-kubeconfig: "true" in a namespace where the proxy's RoleBinding grants Secret read access, so practical risk depends on who holds that Secret-write privilege. No KEV or EPSS data was supplied, and no working public exploit is confirmed in the provided sources; a unit-test fixture in the upstream patch demonstrates an exec stanza. The exec/auth-provider path is fixed upstream in commit 7e4222b (not yet released), while the separate clusters[].server SSRF path is not addressed by that patch.
OSAC operator's console-proxy can be induced to execute an attacker-supplied credential plugin inside its pod, yielding code execution as the osac-console-proxy service account in affected revisions such as 8220502. The issue is high severity (CVSS 8.6) and affects deployments in remote or auto VM cluster mode, with auto the default; deployments using local mode exclusively are unaffected because they do not read kubeconfig Secrets. Exploitation requires a principal able to create or modify a Secret labeled osac.openshift.io/remote-cluster-kubeconfig: "true" in a namespace where the proxy's RoleBinding grants Secret read access, so practical risk depends on who holds that Secret-write privilege. No KEV or EPSS data was supplied, and no working public exploit is confirmed in the provided sources; a unit-test fixture in the upstream patch demonstrates an exec stanza. The exec/auth-provider path is fixed upstream in commit 7e4222b (not yet released), while the separate clusters[].server SSRF path is not addressed by that patch.