CVE-2024-45537

Apache Druid: Users can provide MySQL JDBC properties not on allow list

Published Sep 17, 2024 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
Description
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2024-2821 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.
Github GHSA Github GHSA GHSA-jh66-3545-vpm7 Apache Druid: Users can provide MySQL JDBC properties not on allow list
History
Type Values Removed Values Added
Metrics epss

{'score': 0.00323}

epss

{'score': 0.003}

Type Values Removed Values Added
First Time appeared Apache
Apache druid
Weaknesses NVD-CWE-noinfo
CPEs cpe:2.3:a:apache:druid:*:*:*:*:*:*:*:*
Vendors & Products Apache
Apache druid
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title Apache Druid: Users can provide MySQL JDBC properties not on allow list
Weaknesses CWE-20
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Mar 14, 2025, 3:09 PM
Reserved
Sep 2, 2024, 7:13 AM
Status
Modified
Published
Sep 17, 2024, 7:15 PM
Modified
Jun 17, 2026, 7:54 AM