https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 05:11:07 +0000 https://cve.radiocsirt.org/vuln/certfr-2023-avi-0513 certfr-2023-avi-0513 https://cve.radiocsirt.org/vuln/certfr-2023-avi-0513 https://cve.radiocsirt.org/vuln/cnvd-2023-23554 cnvd-2023-23554 https://cve.radiocsirt.org/vuln/cnvd-2023-23554 https://cve.radiocsirt.org/vuln/euvd-2026-224837 EUVD-2026-224837 https://cve.radiocsirt.org/vuln/euvd-2026-224837 https://cve.radiocsirt.org/vuln/fkie_cve-2023-25194 <p>A possible security vulnerability has been identified in Apache Kafka Connect API. 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 Connect 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&#39;s Kafka clients to &#34;com.sun.security.auth.module.JndiLoginModule&#34;, 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&#39;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.</p> <p>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.</p> <p>Since Apache Kafka 3.4.0, we have added a system property (&#34;-Dorg.apache.kafka.disallowed.…</p> <p>A possible security vulnerability has been identified in Apache Kafka Connect API. 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 Connect 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&#39;s Kafka clients to &#34;com.sun.security.auth.module.JndiLoginModule&#34;, 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&#39;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.</p> <p>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.</p> <p>Since Apache Kafka 3.4.0, we have added a system property (&#34;-Dorg.apache.kafka.disallowed.…</p> https://cve.radiocsirt.org/vuln/fkie_cve-2023-25194 https://cve.radiocsirt.org/vuln/ghsa-26f8-x7cc-wqpc <p><strong>Affected:</strong> Maven: org.apache.kafka:connect</p> <p>A possible security vulnerability has been identified in Apache Kafka Connect API. 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 Connect 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&#39;s Kafka clients to &#34;com.sun.security.auth.module.JndiLoginModule&#34;, 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&#39;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 (&#34;-Dorg.apache.kafka.disallowed.lo…</p> <p><strong>Affected:</strong> Maven: org.apache.kafka:connect</p> <p>A possible security vulnerability has been identified in Apache Kafka Connect API. 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 Connect 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&#39;s Kafka clients to &#34;com.sun.security.auth.module.JndiLoginModule&#34;, 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&#39;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 (&#34;-Dorg.apache.kafka.disallowed.lo…</p> https://cve.radiocsirt.org/vuln/ghsa-26f8-x7cc-wqpc https://cve.radiocsirt.org/vuln/gsd-2023-25194 gsd-2023-25194 https://cve.radiocsirt.org/vuln/gsd-2023-25194 https://cve.radiocsirt.org/vuln/rhsa-2023:1241 <p>Streams: component version with information disclosure flaw kafka: RCE/DoS via SASL JAAS JndiLoginModule configuration in Kafka Connect</p> <p>Streams: component version with information disclosure flaw kafka: RCE/DoS via SASL JAAS JndiLoginModule configuration in Kafka Connect</p> https://cve.radiocsirt.org/vuln/rhsa-2023:1241 https://cve.radiocsirt.org/vuln/wid-sec-w-2023-0300 <p>Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in Apache Kafka ausnutzen, um beliebigen Programmcode auszuführen oder einen Denial of Service Zustand herbeizuführen.</p> <p>Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in Apache Kafka ausnutzen, um beliebigen Programmcode auszuführen oder einen Denial of Service Zustand herbeizuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2023-0300