Skip to content
Fencer Intel
high 7.5

CVE-2019-12399 json

Exposure of Sensitive Information to an Unauthorized Actor in Apache Kafka

published 6y ago modified 4mo ago also GHSA-6jmf-mxwf-r3jc , EUVD-2020-0414

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.9%
EPSS 3.9% chance of exploitation in 30 days, percentile 90%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.apache.kafka:kafka 2.0.2, 2.1.2, 2.2.2, 2.3.1
  • oracle blockchain_platform 21.1.2

Is CVE-2019-12399 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-12399 updated cvss 7.5

kafka: Connect REST API exposes plaintext secrets in tasks endpoint

  • Red Hat AMQ Streams 1
    fixed: vendor fix RHSA-2020:0939
  • Red Hat Decision Manager 7 kafka-clients Red Hat Fuse 7 kafka Red Hat JBoss Fuse 6 kafka Red Hat OpenShift Application Runtimes kafka, kafka-clients Red Hat Process Automation 7 kafka-clients
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.92% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.kafka:kafka
>=2.0.0, <2.0.2
>=2.1.0, <2.1.2
>=2.2.0, <2.2.2
>=2.3.0, <2.3.1
2.0.2
2.1.2
2.2.2
2.3.1

Affected products

  • Apache Kafka

Classification

Weakness
  • CWE-319 Cleartext Transmission of Sensitive Information

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.