CyberRota Analysis
AI-GeneratedStrimzi versions 1.0.0 and earlier are vulnerable, allowing attackers with the ability to create a Kafka custom resource to escalate privileges by manipulating the watchedNamespace parameter. This can lead to the creation of a Role that grants full Secret CRUD permissions in any target namespace, enabling unauthorized access to sensitive data. Organizations using Strimzi for Apache Kafka on Kubernetes or OpenShift should prioritize upgrading to versions 1.0.1 or 1.1.0 to mitigate this high-severity vulnerability.
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
Strimzi provides a way to run an Apache Kafka cluster on Kubernetes or OpenShift in various deployment configurations. In Strimzi 1.0.0 and earlier, an attacker who can create a Kafka custom resource can set Kafka.spec.entityOperator watchedNamespace to a target namespace, causing the Cluster Operator to create a Role with full Secret CRUD permissions there and bind it to the Entity Operator ServiceAccount in the attacker's namespace. The attacker can mint a token for that ServiceAccount and read or write Secrets in any target namespace where the Cluster Operator has been granted permissions, regardless of STRIMZI_NAMESPACE. This issue is fixed in versions 1.0.1 and 1.1.0.