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

CVE-2019-12399 · Severity: low · CVSS 3.1 · Published 2020-05-12

Exposure of Sensitive Information to an Unauthorized Actor in Apache Kafka

Technologies: org.apache.kafka:kafka (Maven). Vendors: Maven.

Quick answers

Is CVE-2019-12399 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2019-12399 being exploited in the wild.
How severe is CVE-2019-12399?
Low severity, with a CVSS score of 3.1, published 12 May 2020.
Which products and versions are affected?
org.apache.kafka:kafka (Maven) ECOSYSTEM:introduced=2.0.0,fixed=2.0.2.
Is there a fix for CVE-2019-12399?
Yes. org.apache.kafka:kafka (Maven): upgrade to 2.0.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2019-12399?
Check whether you run org.apache.kafka:kafka (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.apache.kafka:kafka (Maven): upgrade to 2.0.2 or later
    # set org.apache.kafka:kafka to 2.0.2 in your pom.xml or build.gradle

Affected products

  • org.apache.kafka:kafka (Maven) ECOSYSTEM:introduced=2.0.0,fixed=2.0.2

Identifiers

  • CVE-2019-12399
  • GHSA-6jmf-mxwf-r3jc

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.