CMAK's shared Kafka credentials can let UI users exceed their intended permissions
CMAK, formerly Kafka Manager, is a browser-based tool for administering Apache Kafka clusters and can issue admin requests on the broker's behalf. Its own login controls, such as basic or LDAP authentication, protect the application but do not automatically limit each user to matching Kafka ACLs. Because the Kafka client inside CMAK often uses one broad service credential, a user without direct Kafka access may still perform privileged actions through the interface. The article recommends inventorying cluster connections, separating production from non-production, testing view-only users against direct HTTP requests, protecting stored secrets, and restricting network exposure. A count-only ZoomEye observation found about 1,508 exact-title CMAK matches, though that alone does not prove misconfiguration.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in