Apache Software Foundation Kafka

Apache Kafka: Missing JWT token validation in OAUTHBEARER authentication

In Apache Kafka versions between 0.11.0.0 and 2.1.0, it is possible to manually craft a Produce request which bypasses transaction/idempotent ACL validation. Only authenticated clients with Write permission on the respective topics are able to exploit this vulnerability. Users should upgrade to 2.1.1 or later where this vulnerability has been fixed.

Apache Kafka: Possible RCE attack via SASL JAAS LdapLoginModule configuration

Apache Kafka Clients: Kafka Producer Message Corruption and Misrouting via Buffer Pool Race Condition

Apache Kafka Client: Arbitrary file read and SSRF vulnerability

When Connect workers in Apache Kafka 2.0.0, 2.0.1, 2.1.0, 2.1.1, 2.2.0, 2.2.1, or 2.3.0 are configured with one or more config providers, and a connector is created/updated on that Connect cluster to use an externalized secret variable in a substring of a connector configuration property value, then any client can issue a request to the same Connect cluster to obtain the connector's task configuration and the response will contain the plaintext secret rather than the externalized secrets variables.

Unauthenticated clients may cause OutOfMemoryError on Apache Kafka Brokers

Apache Kafka: Possible RCE/Denial of service attack via SASL JAAS JndiLoginModule configuration

Apache Kafka: Potential incorrect access control during migration from ZK mode to KRaft mode

In Apache Kafka 0.10.0.0 to 0.10.2.1 and 0.11.0.0 to 0.11.0.1, authenticated Kafka clients may use impersonation via a manually crafted protocol message with SASL/PLAIN or SASL/SCRAM authentication when using the built-in PLAIN or SCRAM server implementations in Apache Kafka.

Apache Kafka Clients: Privilege escalation to filesystem read-access via automatic ConfigProvider

Timing Attack Vulnerability for Apache Kafka Connect and Clients

In Eclipse Jetty version 9.4.0.RC0 to 9.4.34.v20201102, 10.0.0.alpha0 to 10.0.0.beta2, and 11.0.0.alpha0 to 11.0.0.beta2, if GZIP request body inflation is enabled and requests from different clients are multiplexed onto a single connection, and if an attacker can send a request with a body that is received entirely but not consumed by the application, then a subsequent request on the same connection will see that body prepended to its body. The attacker will not see any data but may inject data into the body of the subsequent request.

In Apache Kafka 0.9.0.0 to 0.9.0.1, 0.10.0.0 to 0.10.2.1, 0.11.0.0 to 0.11.0.2, and 1.0.0, authenticated Kafka users may perform action reserved for the Broker via a manually created fetch request interfering with data replication, resulting in data loss.

Apache Kafka: SCRAM authentication vulnerable to replay attacks when used without encryption

Apache Kafka, Apache Kafka Clients: Information Exposure Through Network Client Log Output

Apache Kafka: Improper Authorization in CONSUMER_GROUP_DESCRIBE API