Cruise Control for Apache Kafka · Red Hat streams for Apache Kafka 2 · Red Hat streams for Apache Kafka 3
| Product | Affected | Fixed in |
|---|---|---|
| Cruise Control for Apache Kafka |
| No fix yet |
| Red Hat streams for Apache Kafka 2 | — | No fix yet |
| Red Hat streams for Apache Kafka 3 | — | No fix yet |
Cruise Control's Jetty ConstraintSecurityHandler registers security constraints on exact path specs without a catch-all wildcard constraint and without calling setDenyUncoveredHttpMethods(true). The servlet routes requests using Path.of(pathInfo).getFileName(), which strips all leading segments and trailing slashes. Requests like POST /kafkacruisecontrol/x/rebalance bypass authentication entirely but still dispatch to admin endpoints. All 15 admin endpoints become reachable without authentication. In AMQ Streams, the Strimzi operator's NetworkPolicy restricts Cruise Control port 9090 to operator pods only, reducing effective severity to Important.
From the CVE record · redhat
Cruise Control’s Jetty security constraints do not cover certain paths that its servlet still routes to admin endpoints. A network attacker who can reach Cruise Control can use a crafted request path to access all 15 admin endpoints without authentication. In AMQ Streams, the Strimzi operator’s NetworkPolicy restricts Cruise Control port 9090 to operator pods.
Teams running Cruise Control for Apache Kafka or Red Hat streams for Apache Kafka 2 or 3 should check their deployments.