CVE Tools
Track your stack

CVE-2024-32030

Remote code execution via JNDI resolution in JMX metrics collection in Kafka UI

Exploitation likely. EPSS gives it a 51% chance of exploitation in the next 30 days. A vendor fix is available.

CVSS 3.18.1HighEPSS percentile99th51% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFixVendor fixNo build named by the sources

Published Updated Sources: CVE.org, NVD, BDU

NVD CVE.org

What to do

The vendor has published a fix. Version details are below where the sources state them.

  • Provectus Kafka-uiAffected: < 0.7.2Upgrade to: not statedStated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check which version of Kafka UI your team is running.
  2. Check whether dynamic.config.enabled is turned on in your settings, or whether anyone outside your organization has access to the connected Kafka cluster.
  3. Upgrade Kafka UI to version 0.7.2 or later.
  4. Confirm Kafka UI is not exposed directly to the internet and that only trusted brokers can connect to it.
  5. There is no temporary workaround — upgrading is the only fix.
Some work to apply
Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

Kafka UI is an Open-Source Web UI for Apache Kafka Management. Kafka UI API allows users to connect to different Kafka brokers by specifying their network address and port. As a separate feature, it also provides the ability to monitor the performance of Kafka brokers by connecting to their JMX ports. JMX is based on the RMI protocol, so it is inherently susceptible to deserialization attacks. A potential attacker can exploit this feature by connecting Kafka UI backend to its own malicious broker. This vulnerability affects the deployments where one of the following occurs: 1. dynamic.config.enabled property is set in settings. It's not enabled by default, but it's suggested to be enabled in many tutorials for Kafka UI, including its own README.md. OR 2. an attacker has access to the Kafka cluster that is being connected to Kafka UI. In this scenario the attacker can exploit this vulnerability to expand their access and execute code on Kafka UI as well. Instead of setting up a legitimate JMX port, an attacker can create an RMI listener that returns a malicious serialized object for any RMI call. In the worst case it could lead to remote code execution as Kafka UI has the required gadget chains in its classpath. This issue may lead to post-auth remote code execution. This is particularly dangerous as Kafka-UI does not have authentication enabled by default. This issue has been addressed in version 0.7.2. All users are advised to upgrade. There are no known workarounds for this vulnerability. These issues were discovered and reported by the GitHub Security lab and is also tracked as GHSL-2023-230.

In plain language

Written by AI from the record

If you run Kafka UI to manage your Kafka message queues, a flaw in how it connects to monitoring ports could let an attacker take over the server — update to version 0.7.2 to be safe.

Kafka UI's JMX-based broker monitoring feature deserializes RMI responses from connected Kafka brokers without validation, letting an attacker-controlled broker or JMX endpoint send a malicious serialized object that achieves remote code execution via known gadget chains in the classpath (fixed in 0.7.2).

If you're affected

  • Full server takeover
  • Access to Kafka cluster data
  • No login required by default
  • Operational disruption of monitoring/management

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS99th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

51% chance of exploitation activity in the next 30 days, which ranks it in the 99th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

8 events over 844 days, from the signal feeds we watch.

  1. EPSS band changemoderate → highepss band change
  2. EPSS band changehigh → moderate
  3. Patch availablerecord updated
  4. Publishedweakness classified, att&ck mapped

Affected products

And 1 more affected product. See all after sign-in

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Scored 8.1 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

And 5 more references. See all after sign-in

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Kafka-ui, not every advisory.