# CVE-2024-32030: Remote code execution via JNDI resolution in JMX metrics collection in Kafka UI > Attackers can achieve remote code execution in Kafka UI by exploiting JMX deserialization flaws when dynamic configuration is enabled or cluster access is compromised. - **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 19 Jun 2024 - **Updated:** 2 Aug 2024 ## What is CVE-2024-32030? CVE-2024-32030 is a high-severity unsafe deserialization vulnerability in provectus kafka-ui, published on 19 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-94 (Improper Control of Generation of Code), CWE-502 (Deserialization of Untrusted Data) ## Which versions are affected by CVE-2024-32030? ## How do I fix CVE-2024-32030? No fix has been published for CVE-2024-32030 yet. Limit exposure of the affected software until one is available. ## Is CVE-2024-32030 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-32030 exists. Public exploit code: - https://github.com/huseyinstif/CVE-2024-32030-Nuclei-Template (github_poc): https://github.com/huseyinstif/CVE-2024-32030-Nuclei-Template ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-32030 and fix it if it is affected. What it is: CVE-2024-32030 is a high-severity unsafe deserialization vulnerability in provectus kafka-ui, published on 19 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-32030 exists. Affected product: provectus kafka-ui. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-32030/ (Markdown: https://insights.sbomify.com/CVE-2024-32030/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-32030 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-32030 - OSV: https://osv.dev/vulnerability/CVE-2024-32030 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-32030/ Summaries are generated and may contain mistakes; the official description above is the record.