CVE-2019-12399: Apache Kafka - Exposure of Sensitive Information to an Unauthorized Actor

org.apache.kafka:kafka Updated 02 Oct 2025

Summary

12/05/2020
Yes i
High
7.5

CVE-2019-12399: Exposure of Sensitive Information to an Unauthorized Actor in Apache Kafka. Affects org.apache.kafka:kafka across 4 version ranges.

>= 2.0.0, < 2.0.2 >= 2.1.0, < 2.1.2 >= 2.2.0, < 2.2.2 >= 2.3.0, < 2.3.1

Fixed in 4 releases; the minimum fixed version depends on the release line you run. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Apache Kafka is an open-source distributed event streaming platform used for building real-time data pipelines and streaming applications. It provides a high-throughput, fault-tolerant, and scalable messaging system. The vulnerability identified as CVE-2019-12399 affects Apache Kafka versions 2.0.0 to 2.3.0. This vulnerability allows an unauthorized actor to access sensitive information by exploiting a configuration issue in Connect workers when using externalized secret variables in connector configuration properties.

Vulnerability Detail

The vulnerability arises when Connect workers are configured with one or more config providers and a connector is created or updated to use an externalized secret variable in a substring of a connector configuration property value. In such cases, any client can send a request to the Connect cluster and retrieve the plaintext secret instead of the externalized secret variable. This exposes sensitive information to unauthorized actors. The impact of this vulnerability can be severe, as it allows unauthorized access to confidential data and can lead to data breaches or unauthorized system access.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 2.0.0, < 2.0.2 2.0.2
  • >= 2.1.0, < 2.1.2 2.1.2
  • >= 2.2.0, < 2.2.2 2.2.2
  • >= 2.3.0, < 2.3.1 2.3.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There is no specific workaround provided for this vulnerability. The recommended approach is to upgrade to a fixed version of Apache Kafka.

Conclusion

The vulnerability CVE-2019-12399 in Apache Kafka exposes sensitive information to unauthorized actors. To mitigate this risk, it is crucial to upgrade to a fixed version of Apache Kafka (2.0.2, 2.1.2, 2.2.2, or 2.3.1) and review connector configurations. For further assistance with vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.apache.kafka:kafka →

Share this vulnerability

FAQ

Apache Kafka is an open-source distributed event streaming platform used for building real-time data pipelines and streaming applications.

The vulnerability affects Apache Kafka versions 2.0.0 to 2.3.0.

The vulnerability exposes sensitive information to unauthorized actors, potentially leading to data breaches or unauthorized system access.

To fix this vulnerability, it is recommended to upgrade to a fixed version of Apache Kafka (2.0.2, 2.1.2, 2.2.2, or 2.3.1) and review/update connector configurations.

No specific workaround is provided. Upgrading to a fixed version is the recommended approach.

Related vulnerabilities

Recent vulnerabilities recorded for org.apache.kafka:kafka.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 2.0.0, < 2.0.2 2.0.2
  • >= 2.1.0, < 2.1.2 2.1.2
  • >= 2.2.0, < 2.2.2 2.2.2
  • >= 2.3.0, < 2.3.1 2.3.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback