Cruise-control: streams for apache kafka cruise control: authentication bypass via extra path segment allows unauthenticated access to all admin endpoints

Overview

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.

Affected

• cruise_control_for_apache_kafka >= 2.0.82 < 3.1.0
• cruise-control (all versions)
• cruise-control (all versions)

Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.

Workarounds

1. Verify Strimzi NetworkPolicy exists restricting CC :9090 to operator pods
2. Do not expose CC :9090 via Ingress or Route — must not be externally accessible
3. Confirm TLS is enabled on the CC HTTP endpoint (Strimzi default)
4. For standalone CC: deploy path-normalizing reverse proxy and restrict :9090 via firewall