- Veröffentlicht
- 10.06.2025 09:52
- Zuletzt geändert
- 08.09.2026
- EPSS (30 Tage)
- 1.1 %
- CVSS-Vektor
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Beschreibung
Originaltext der Quelle, nicht übersetzt.
A possible security vulnerability has been identified in Apache Kafka.
This requires access to a alterConfig to the cluster resource, or 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 clusters since Apache Kafka 2.0.0 (Kafka Connect 2.3.0).
When configuring the broker via config file or AlterConfig command, or connector via the Kafka 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.LdapLoginModule", 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.9.1/4.0.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,com.sun.security.auth.module.LdapLoginModule" are disabled in Apache Kafka Connect 3.9.1/4.0.0.
We advise the Kafka users to validate connector configurations and only allow trusted LDAP 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.
Status beim Hersteller
Red Hat stuft seine Produktlinien ein: 1 behoben, 21 nicht betroffen.
Nicht betroffen (21)
A-MQ Clients 2Nicht betroffenverwundbarer Code nicht enthaltenkafka-clients
Logging Subsystem for Red Hat OpenShiftNicht betroffenverwundbarer Code nicht enthaltenkafka-clients, kafka_2.11
OpenShift ServerlessNicht betroffenverwundbarer Code nicht enthaltenopenshift-serverless-1/kn-ekb-dispatcher-rhel8, openshift-serverless-1/kn-ekb-kafka-controller-rhel8, openshift-serverless-1/kn-ekb-post-install-rhel8, openshift-serverless-1/kn-ekb-receiver-rhel8, openshift-serverless-1/kn-ekb-webhook-kafka-rhel8, openshift-serverless-1/kn-eventing-istio-controller-rhel8
Red Hat Data Grid 8Nicht betroffenverwundbarer Code nicht enthaltenkafka-clients
Red Hat Enterprise Linux 8Nicht betroffenverwundbarer Code nicht enthaltenlog4j, log4j-jcl, log4j-slf4j, log4j-web
Red Hat Enterprise Linux 9Nicht betroffenverwundbarer Code nicht enthaltenlog4j, log4j-jcl, log4j-slf4j
Red Hat Fuse 7Nicht betroffenverwundbarer Code nicht enthaltenconnect, connect-api, connect-basic-auth-extension, connect-file, connect-json, connect-mirror, connect-mirror-client, connect-runtime, connect-transforms, jmh-benchmarks, kafka, kafka-build-project, kafka-clients, kafka-examples, kafka-licenses, kafka-log4j-appender, kafka-metadata, kafka-raft, kafka-streams, kafka-streams-examples, kafka-streams-scala_2.12, kafka-streams-test-utils, kafka-tools, kafka_2.12, kafka_2.13 und 1 weitere
Red Hat Integration Camel K 1Nicht betroffenverwundbarer Code nicht enthaltenconnect-api, connect-file, connect-json, connect-runtime, connect-transforms, kafka-clients, kafka-log4j-appender, kafka-streams, kafka-tools, kafka_2.12
Red Hat JBoss Enterprise Application Platform 7Nicht betroffenverwundbarer Code nicht enthaltenconnect, connect-api, connect-basic-auth-extension, connect-file, connect-json, connect-mirror, connect-mirror-client, connect-runtime, connect-transforms, generator, kafka, kafka-build-project, kafka-clients, kafka-examples, kafka-log4j-appender, kafka-metadata, kafka-raft, kafka-server-common, kafka-shell, kafka-storage, kafka-storage-api, kafka-streams, kafka-streams-examples, kafka-streams-scala_2.13, kafka-streams-test-utils und 20 weitere
Red Hat JBoss Enterprise Application Platform 8Nicht betroffenverwundbarer Code nicht enthaltenconnect, connect-api, connect-basic-auth-extension, connect-file, connect-json, connect-mirror, connect-mirror-client, connect-runtime, connect-test-plugins, connect-transforms, generator, kafka, kafka-build-project, kafka-clients, kafka-examples, kafka-group-coordinator, kafka-log4j-appender, kafka-metadata, kafka-raft, kafka-server, kafka-server-common, kafka-shell, kafka-storage, kafka-storage-api, kafka-streams und 31 weitere
Red Hat JBoss Enterprise Application Platform Expansion PackNicht betroffenverwundbarer Code nicht enthaltenconnect, connect-api, connect-basic-auth-extension, connect-file, connect-json, connect-mirror, connect-mirror-client, connect-runtime, connect-test-plugins, connect-transforms, generator, kafka, kafka-build-project, kafka-clients, kafka-examples, kafka-group-coordinator, kafka-log4j-appender, kafka-metadata, kafka-raft, kafka-server, kafka-server-common, kafka-shell, kafka-storage, kafka-storage-api, kafka-streams und 31 weitere
Red Hat Process Automation 7Nicht betroffenverwundbarer Code nicht enthaltenkafka-clients
Red Hat build of Apache Camel 4 for Quarkus 3Nicht betroffenverwundbarer Code nicht enthaltenquarkus-camel-bom, quarkus-cxf-bom
Red Hat build of Apache Camel for Spring Boot 4Nicht betroffenverwundbarer Code nicht enthaltenconnect-api, connect-file, connect-json, connect-runtime, connect-transforms, kafka-clients, kafka-group-coordinator, kafka-group-coordinator-api, kafka-metadata, kafka-raft, kafka-server, kafka-server-common, kafka-storage, kafka-storage-api, kafka-tools-api, kafka-transaction-coordinator, kafka_2.13
Red Hat build of Apicurio Registry 2Nicht betroffenverwundbarer Code nicht enthaltenconnect-api, connect-json, kafka-clients, kafka-streams
Red Hat build of Apicurio Registry 3Nicht betroffenverwundbarer Code nicht enthaltenconnect-api, connect-json, kafka-clients
Red Hat build of Debezium 2Nicht betroffenverwundbarer Code nicht enthaltenconnect-api, connect-file, connect-json, connect-runtime, connect-transforms, kafka-clients, kafka-group-coordinator, kafka-metadata, kafka-raft, kafka-server, kafka-server-common, kafka-storage, kafka-storage-api, kafka-tools-api, kafka_2.13
Red Hat build of Debezium 3Nicht betroffenverwundbarer Code nicht enthaltenconnect-api, connect-file, connect-json, connect-runtime, connect-transforms, kafka-clients, kafka-group-coordinator, kafka-group-coordinator-api, kafka-metadata, kafka-raft, kafka-server, kafka-server-common, kafka-storage, kafka-storage-api, kafka-tools-api, kafka-transaction-coordinator, kafka_2.13
Red Hat build of QuarkusNicht betroffenverwundbarer Code nicht enthaltenquarkus-bom
streams for Apache KafkaNicht betroffenverwundbarer Code nicht enthaltenconnect, connect-api, connect-basic-auth-extension, connect-file, connect-json, connect-mirror, connect-mirror-client, connect-runtime, connect-transforms, generator, kafka, kafka-build-project, kafka-clients, kafka-examples, kafka-group-coordinator, kafka-log4j-appender, kafka-metadata, kafka-raft, kafka-server-common, kafka-shell, kafka-storage, kafka-storage-api, kafka-streams, kafka-streams-examples, kafka-streams-scala_2.13 und 26 weitere
streams for Apache Kafka 2Nicht betroffenverwundbarer Code nicht enthaltenconnect, connect-api, connect-basic-auth-extension, connect-file, connect-json, connect-mirror, connect-mirror-client, connect-runtime, connect-test-plugins, connect-transforms, generator, kafka, kafka-build-project, kafka-clients, kafka-examples, kafka-group-coordinator, kafka-group-coordinator-api, kafka-log4j-appender, kafka-metadata, kafka-raft, kafka-server, kafka-server-common, kafka-shell, kafka-storage, kafka-storage-api und 34 weitere
Betroffene Pakete im beobachteten Stack
CVEApache Software Foundation/Apache Kafkakein Fix bekanntCVE-2025-27818
Mavenorg.apache.kafka:kafka_2.11kein Fix bekanntGHSA-76qp-h5mr-frr4
Mavenorg.apache.kafka:kafka_2.122.3.0 → 3.9.1GHSA-76qp-h5mr-frr4
Mavenorg.apache.kafka:kafka_2.132.4.0 → 3.9.1GHSA-76qp-h5mr-frr4
NVDapache:kafka2.3.0 → 3.9.1CVE-2025-27818
Weitere betroffene Pakete (4)
Bitnamikafka2.3.0 → 3.9.1BIT-kafka-2025-27818
TuxCare:Mavenorg.apache.kafka:kafka-clients3.2.3.tuxcare.1CLSA-2025-1752019395
TuxCare:Mavenorg.apache.kafka:kafka_2.123.2.3.tuxcare.1CLSA-2025-1752019395
TuxCare:Mavenorg.apache.kafka:kafka_2.133.2.3.tuxcare.1CLSA-2025-1752019395
Empfohlene Prüfung
- Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
- Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
- Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · mit Login) ist aus dem CVSS-Vektor abgeleitet.
Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.
Referenzen
- kafka.apache.org/cve-list
- www.openwall.com/lists/oss-security/2025/06/09/2
- nvd.nist.gov/vuln/detail/CVE-2025-27818
- github.com/apache/kafka
- security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-27818.json
- access.redhat.com/security/cve/CVE-2025-27818
- bugzilla.redhat.com/show_bug.cgi
- www.cve.org/CVERecord