org.apache.kafka:kafka-clients vulnerabilities
- Registry
- Maven
- Latest
- 4.4.0
- License
- The Apache License, Version 2.0
7 known advisories
The latest version, 4.4.0, is not affected by any of them. Projects on older versions may be.
mvn versions:use-dep-version -Dincludes=org.apache.kafka:kafka-clients -DdepVersion=4.4.0 -DforceVersion=trueIs your project on an affected org.apache.kafka:kafka-clients?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for org.apache.kafka:kafka-clients
Apache Kafka does not validate JWT tokens in its OAUTHBEARER authentication implementation
- Affected
- >=4.1.0 <4.1.2
- Fixed in
- 4.1.2
Apache Kafka exposes sensitive information in its DEBUG logs
- Affected
- >=0.11.0 <3.9.2 · >=4.0.0 <4.0.1
- Fixed in
- 3.9.2, 4.0.1
Apache Kafka Clients: Kafka Producer Message Corruption and Misrouting via Buffer Pool Race Condition
- Affected
- >=2.8.0 <3.9.2 · >=4.0.0 <4.0.2 · >=4.1.0 <4.1.2
- Fixed in
- 3.9.2, 4.0.2, 4.1.2
Apache Kafka Client Arbitrary File Read and Server Side Request Forgery Vulnerability
- Affected
- >=3.1.0 <3.9.1
- Fixed in
- 3.9.1
Apache Kafka Clients: Privilege escalation to filesystem read-access via automatic ConfigProvider
- Affected
- >=2.3.0 <3.7.1
- Fixed in
- 3.7.1
Improper Authentication in Apache Kafka
- Affected
- >=0.10.0.0 <0.10.2.2 · >=0.11.0.0 <0.11.0.2
- Fixed in
- 0.10.2.2, 0.11.0.2
Observable Discrepancy in Apache Kafka
- Affected
- >=2.0.0 <2.6.3 · >=2.7.0 <2.7.2 · >=2.8.0 <2.8.1
- Fixed in
- 2.6.3, 2.7.2, 2.8.1
Is your org.apache.kafka:kafka-clients version vulnerable?
- org.apache.kafka:kafka-clients 4.4No known advisories in 4.4.0
- org.apache.kafka:kafka-clients 4.3No known advisories in 4.3.2
- org.apache.kafka:kafka-clients 4.2No known advisories in 4.2.2
- org.apache.kafka:kafka-clients 4.1No known advisories in 4.1.2
- org.apache.kafka:kafka-clients 4.0No known advisories in 4.0.2
- org.apache.kafka:kafka-clients 3.9No known advisories in 3.9.2
- org.apache.kafka:kafka-clients 3.83 advisories in 3.8.1
- org.apache.kafka:kafka-clients 3.73 advisories in 3.7.2
- org.apache.kafka:kafka-clients 3.64 advisories in 3.6.2
- org.apache.kafka:kafka-clients 3.54 advisories in 3.5.2
- org.apache.kafka:kafka-clients 3.44 advisories in 3.4.1
- org.apache.kafka:kafka-clients 2.83 advisories in 2.8.2
- org.apache.kafka:kafka-clients 2.72 advisories in 2.7.2
- org.apache.kafka:kafka-clients 2.62 advisories in 2.6.3
- org.apache.kafka:kafka-clients 2.53 advisories in 2.5.1
- org.apache.kafka:kafka-clients 2.43 advisories in 2.4.1
- org.apache.kafka:kafka-clients 2.33 advisories in 2.3.1
Which of your client projects still run an old org.apache.kafka:kafka-clients?
NPMscan reads the pom.xml, build.gradle and gradle.lockfile in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Maven packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Maven registry.