Streamshub Console For Apache Kafka
Monthly
Cross-tenant privilege escalation in StreamsHub Console for Apache Kafka allows an authenticated Kubernetes tenant that can create or modify Console custom resources to point spec.containers.api.spec.image at an arbitrary container image, which the operator then deploys into a pod running under a ServiceAccount bound by ClusterRoleBinding to cluster-wide Strimzi CRD read access, Kafka/KafkaRebalance patch rights, and cluster-monitoring-view. The attacker-controlled code reads the projected ServiceAccount token and gains read/write control over the Strimzi control plane across tenant boundaries, with high confidentiality and integrity impact (CVSS 9.9, scope changed). Exploitation is gated by the tenant-level RBAC permission rather than being open to the internet, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Credential theft in multi-tenant Red Hat StreamsHub Console for Apache Kafka and Streams for Apache Kafka 2/3 deployments is possible because the operator trusts a namespace field supplied in a Console custom resource. An authenticated tenant with permission to create Console CRs (PR:L) can point spec.kafkaClusters[].credentials.kafkaUser.namespace at a victim namespace, causing the cluster-wide-privileged operator to read that namespace’s KafkaUser Secret-SASL credentials or TLS private keys-and write the plaintext into a Secret in the attacker’s namespace. CVSS 3.1 scores this 7.7 with scope changed and high confidentiality impact; no public exploit identified at time of analysis, so risk is concentrated in multi-tenant clusters where untrusted users can create Console resources.
Cross-tenant privilege escalation in StreamsHub Console for Apache Kafka allows an authenticated Kubernetes tenant that can create or modify Console custom resources to point spec.containers.api.spec.image at an arbitrary container image, which the operator then deploys into a pod running under a ServiceAccount bound by ClusterRoleBinding to cluster-wide Strimzi CRD read access, Kafka/KafkaRebalance patch rights, and cluster-monitoring-view. The attacker-controlled code reads the projected ServiceAccount token and gains read/write control over the Strimzi control plane across tenant boundaries, with high confidentiality and integrity impact (CVSS 9.9, scope changed). Exploitation is gated by the tenant-level RBAC permission rather than being open to the internet, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Credential theft in multi-tenant Red Hat StreamsHub Console for Apache Kafka and Streams for Apache Kafka 2/3 deployments is possible because the operator trusts a namespace field supplied in a Console custom resource. An authenticated tenant with permission to create Console CRs (PR:L) can point spec.kafkaClusters[].credentials.kafkaUser.namespace at a victim namespace, causing the cluster-wide-privileged operator to read that namespace’s KafkaUser Secret-SASL credentials or TLS private keys-and write the plaintext into a Secret in the attacker’s namespace. CVSS 3.1 scores this 7.7 with scope changed and high confidentiality impact; no public exploit identified at time of analysis, so risk is concentrated in multi-tenant clusters where untrusted users can create Console resources.