You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Path to dependency file: /dd-java-agent/instrumentation/kafka-streams-0.11/kafka-streams-0.11.gradle
Path to vulnerable library: /caches/modules-2/files-2.1/org.apache.kafka/kafka-clients/2.8.1/cf4abb87e0d49670cf7a94e79eba14616be27418/kafka-clients-2.8.1.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.kafka/kafka-clients/2.8.1/cf4abb87e0d49670cf7a94e79eba14616be27418/kafka-clients-2.8.1.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.kafka/kafka-clients/2.8.1/cf4abb87e0d49670cf7a94e79eba14616be27418/kafka-clients-2.8.1.jar,/caches/modules-2/files-2.1/org.apache.kafka/kafka-clients/2.8.1/cf4abb87e0d49670cf7a94e79eba14616be27418/kafka-clients-2.8.1.jar
A possible security vulnerability has been identified in Apache Kafka Connect. 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. When configuring the connector via the Kafka Connect REST API, an authenticated operator can set the sasl.jaas.config property for any of the connector's Kafka clients to "com.sun.security.auth.module.JndiLoginModule", which can be done via the producer.override.sasl.jaas.config, consumer.override.sasl.jaas.config, or admin.override.sasl.jaas.config properties. 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. Attacker can cause unrestricted deserialization of untrusted data (or) RCE vulnerability when there are gadgets in the classpath. 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. 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.4.0, we have added a system property ("-Dorg.apache.kafka.disallowed.login.modules") to disable the problematic login modules usage in SASL JAAS configuration. Also by default "com.sun.security.auth.module.JndiLoginModule" is disabled in Apache Kafka 3.4.0. We advise the Kafka Connect users to validate connector configurations and only allow trusted JNDI configurations. Also examine connector dependencies for vulnerable versions and either upgrade their connectors, upgrading that specific dependency, or removing the connectors as options for remediation. Finally, in addition to leveraging the "org.apache.kafka.disallowed.login.modules" system property, Kafka Connect users can also implement their own connector client config override policy, which can be used to control which Kafka client properties can be overridden directly in a connector config and which cannot.
mend-for-jackfan.us.kgbot
changed the title
CVE-2023-25194 (High) detected in kafka-clients-2.8.1.jar
CVE-2023-25194 (Medium) detected in kafka-clients-2.8.1.jar
Mar 7, 2023
mend-for-jackfan.us.kgbot
changed the title
CVE-2023-25194 (Medium) detected in kafka-clients-2.8.1.jar
CVE-2023-25194 (Medium) detected in kafka-clients-2.8.1.jar - autoclosed
Jun 20, 2023
✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.
CVE-2023-25194 - Medium Severity Vulnerability
Library home page: https://kafka.apache.org
Path to dependency file: /dd-java-agent/instrumentation/kafka-streams-0.11/kafka-streams-0.11.gradle
Path to vulnerable library: /caches/modules-2/files-2.1/org.apache.kafka/kafka-clients/2.8.1/cf4abb87e0d49670cf7a94e79eba14616be27418/kafka-clients-2.8.1.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.kafka/kafka-clients/2.8.1/cf4abb87e0d49670cf7a94e79eba14616be27418/kafka-clients-2.8.1.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.kafka/kafka-clients/2.8.1/cf4abb87e0d49670cf7a94e79eba14616be27418/kafka-clients-2.8.1.jar,/caches/modules-2/files-2.1/org.apache.kafka/kafka-clients/2.8.1/cf4abb87e0d49670cf7a94e79eba14616be27418/kafka-clients-2.8.1.jar
Dependency Hierarchy:
Found in HEAD commit: 2819174635979a19573ec0ce8e3e2b63a3848079
Found in base branch: master
A possible security vulnerability has been identified in Apache Kafka Connect. 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. When configuring the connector via the Kafka Connect REST API, an authenticated operator can set the
sasl.jaas.config
property for any of the connector's Kafka clients to "com.sun.security.auth.module.JndiLoginModule", which can be done via theproducer.override.sasl.jaas.config
,consumer.override.sasl.jaas.config
, oradmin.override.sasl.jaas.config
properties. 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. Attacker can cause unrestricted deserialization of untrusted data (or) RCE vulnerability when there are gadgets in the classpath. 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. 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.4.0, we have added a system property ("-Dorg.apache.kafka.disallowed.login.modules") to disable the problematic login modules usage in SASL JAAS configuration. Also by default "com.sun.security.auth.module.JndiLoginModule" is disabled in Apache Kafka 3.4.0. We advise the Kafka Connect users to validate connector configurations and only allow trusted JNDI configurations. Also examine connector dependencies for vulnerable versions and either upgrade their connectors, upgrading that specific dependency, or removing the connectors as options for remediation. Finally, in addition to leveraging the "org.apache.kafka.disallowed.login.modules" system property, Kafka Connect users can also implement their own connector client config override policy, which can be used to control which Kafka client properties can be overridden directly in a connector config and which cannot.Publish Date: 2023-02-07
URL: CVE-2023-25194
Base Score Metrics:
Type: Upgrade version
Origin: https://kafka.apache.org/cve-list
Release Date: 2023-02-07
Fix Resolution: 3.4.0
⛑️ Automatic Remediation is available for this issue
The text was updated successfully, but these errors were encountered: