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.
Attack Parameters
Attack Vector
Adjacent
Requires local network access
Attack Complexity
High
Difficult to exploit
Privileges Required
Low
Basic privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
High
Complete data leak
Integrity
High
Complete data modification
Availability
High
Complete denial of service
CVSS Vector v3.1
Weakness Type (CWE)
References 6
https://github.com/strimzi/strimzi-kafka-operator/commit/b3bfeffcc30754c3e62e6f…
security-advisories@github.com
https://github.com/strimzi/strimzi-kafka-operator/commit/f6c5207ba7ec89b46ce672…
security-advisories@github.com
https://github.com/strimzi/strimzi-kafka-operator/pull/12844
security-advisories@github.com
https://github.com/strimzi/strimzi-kafka-operator/releases/tag/1.0.1
security-advisories@github.com
https://github.com/strimzi/strimzi-kafka-operator/releases/tag/1.1.0
security-advisories@github.com
https://github.com/strimzi/strimzi-kafka-operator/security/advisories/GHSA-mw9r…
security-advisories@github.com