GitHub Advisoryadvisory · Maven
GHSA-jh66-3545-vpm7 Apache Druid: Users can provide MySQL JDBC properties not on allow list
LOW
Official page ↗
- Aliases
- CVE-2024-45537
- Ecosystem
- Maven
- Packages
- org.apache.druid:druid
- Severity
- Low
- CVSS vector
- CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
- Weaknesses
- CWE-20
- Reviewed
- 2024-09-17
Affected packages
• Maven org.apache.druid:druid: < 30.0.1 → fixed in 30.0.1
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.
Related
Alias · CVE (1)
- CVE-2024-45537 Apache Druid allows users with certain permissions to read data from other database systems using JDBC. vulnerability
Weakness · CWE (1)
- CWE-20 Improper Input Validation weakness