CVE-2024-32030
Last modified
CVE-2024-32030 is a high-severity vulnerability rated 8.1/10 on the CVSS scale. 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. EPSS estimates a 34.09% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2024-32030?
How severe is CVE-2024-32030?
How do I fix CVE-2024-32030?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-32025Kohya_ss is a GUI for Kohya's Stable Diffusion trainers. Koh…9.1
- CVE-2024-32026Kohya_ss is a GUI for Kohya's Stable Diffusion trainers. Koh…9.8
- CVE-2024-32027Kohya_ss is a GUI for Kohya's Stable Diffusion trainers. Koh…9.8
- CVE-2024-32028OpenTelemetry dotnet is a dotnet telemetry framework. In aff…4.1
- CVE-2024-32029Rejected reason: This CVE is a duplicate of another CVE.
- CVE-2024-3203A vulnerability, which was classified as critical, was found…9.8
- CVE-2024-32034decidim is a Free Open-Source participatory democracy, citiz…4.8
- CVE-2024-32035ImageSharp is a 2D graphics API. A vulnerability discovered …6.5
- CVE-2024-32036ImageSharp is a 2D graphics API. A data leakage flaw was fou…6.5
- CVE-2024-32037GeoNetwork is a catalog application to manage spatially refe…5.3
- CVE-2024-32038Wazuh is a free and open source platform used for threat pre…9.8
- CVE-2024-32039FreeRDP is a free implementation of the Remote Desktop Proto…9.8
Are you affected by CVE-2024-32030?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
