We advise the Kafka Connect users to validate connector configurations and only allow trusted JNDI configurations. Also by default '.module.JndiLoginModule' is disabled in Apache Kafka 3.4.0. Since Apache Kafka 3.4.0, we have added a system property ('.login.modules') to disable the problematic login modules usage in SASL JAAS configuration. Before Apache Kafka 3.0.0, users may not specify these properties unless the Kafka Connect cluster has been reconfigured with a connector client override policy that permits them. Since Apache Kafka 3.0.0, users are allowed to specify these properties in connector configurations for Kafka Connect clusters running with out-of-the-box configurations. Attacker can cause unrestricted deserialization of untrusted data (or) RCE vulnerability when there are gadgets in the classpath. This will allow the server to connect to the attacker's LDAP server and deserialize the LDAP response, which the attacker can use to execute java deserialization gadget chains on the Kafka connect server.

When configuring the connector via the Kafka Connect REST API, an authenticated operator can set the `` property for any of the connector's Kafka clients to '.module.JndiLoginModule', which can be done via the `.config`, `.config`, or `.config` properties.

This requires access to a Kafka Connect worker, and the ability to create/modify connectors on it with an arbitrary Kafka client SASL JAAS config and a SASL-based security protocol, which has been possible on Kafka Connect clusters since Apache Kafka 2.3.0. An LDAP Injection vulnerability exists in the LdapIdentityBackend of Apache Kerby before 2.0.3.Ī possible security vulnerability has been identified in Apache Kafka Connect.

Vms free edition communigate pro server