CVE-2024-45537: Apache Druid: Users can provide MySQL JDBC properties not on allow list
Apache Druid allows users with certain permissions to read data from other database systems using JDBC. This functionality allows trusted users to set up Druid lookups or run ingestion tasks. Druid also allows administrators to configure a list of allowed properties that users are able to provide for their JDBC connections. By default, this allowed properties list restricts users to TLS-related properties only. However, when configuration a MySQL JDBC connection, users can use a particularly-crafted JDBC connection string to provide properties that are not on this allow list.
Users without the permission to configure JDBC connections are not able to exploit this vulnerability. CVE-2021-26919 describes a similar vulnerability which was partially addressed in Apache Druid 0.20.2.
This issue is fixed in Apache Druid 30.0.1.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2024-45537?
The severity of CVE-2024-45537 is categorized based on its potential impact on the security of Apache Druid.
How do I fix CVE-2024-45537?
To fix CVE-2024-45537, upgrade Apache Druid to version 30.0.1 or higher.
What versions of Apache Druid are affected by CVE-2024-45537?
CVE-2024-45537 affects Apache Druid versions prior to 30.0.1.
What are the implications of CVE-2024-45537?
CVE-2024-45537 allows users with certain permissions to read data from other databases, which could lead to unauthorized data access.
Who is impacted by CVE-2024-45537?
Users of Apache Druid with specific permissions are primarily impacted by CVE-2024-45537.