dbcve.org
DruidApplication · Apache

CVE-2024-45537

MEDIUM · 6.5 CVSS v3.1 Published 2024-09-17
Fix available
A fix is available. Upgrade to 30.0.1 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Druid has an access control bypass in its JDBC connection configuration. Users with permissions to configure JDBC connections can use a specially-crafted MySQL JDBC connection string to provide properties outside the allowed properties list (which defaults to TLS-only), potentially enabling unauthorized data access from other database systems.

MitigationUpgrade Apache Druid to version 30.0.1 or later to obtain the fix. Additionally, audit and restrict JDBC connection permissions for users who should not have this capability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DruidApplication
Affected:< 30.0.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Apache Druid version
    Run the Druid version command or check the DruidAbout page in the web console to determine the exact version number
    Affected if The installed version is lower than 30.0.1
  2. Verify JDBC connection permission configuration
    Review Druid's access control configuration to determine which users or roles have permissions to create or modify JDBC connection strings
    Affected if Non-admin users or untrusted roles have permission to configure JDBC connections
  3. Examine existing JDBC connection string definitions
    Inspect the JDBC connection configuration files or database connector settings in the Druid console or configuration system for any MySQL JDBC connection strings
    Affected if A MySQL JDBC connection string exists that includes properties beyond the default TLS-only allowed list
  4. Check for properties outside allowed list
    Review any configured JDBC connection strings to identify if they contain properties such as 'allowLoadLocalInfile', 'allowUrlInLocalInfile', or other properties that could enable arbitrary data access
    Affected if Any JDBC connection string contains properties not in the default TLS-only allowed properties list

A user is affected if running Apache Druid version below 30.0.1 AND having users with JDBC connection configuration permissions AND a MySQL JDBC connection string with properties outside the TLS-only default list exists in the environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 30.0.1 or later
Fixed in 30.0.1
Interim mitigation

Upgrade Apache Druid to version 30.0.1 or later to obtain the fix. Additionally, audit and restrict JDBC connection permissions for users who should not have this capability.

Recommended fix High confidence

30.0.1

  1. Verify current Apache Druid version using bin/druid version or management console
  2. Plan maintenance window for upgrade
  3. Back up Druid metadata store and any custom configurations
  4. Download Apache Druid 30.0.1 from official Apache download mirrors
  5. Stop all Druid services gracefully
  6. Replace Druid installation with version 30.0.1
  7. Review and restore any custom configuration files if needed
  8. Start Druid services in order (ZooKeeper, then Broker, then Coordinator, then Overlord, then Historical, then MiddleManager)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Druid Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-45537 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-45537 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data