dbcve.org
DruidApplication · Apache

CVE-2024-45384

MEDIUM · 5.3 CVSS v3.1 Published 2024-09-17
Fix available
A fix is available. Upgrade to 30.0.1 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Padding Oracle vulnerability in Apache Druid extension, druid-pac4j. This could allow an attacker to manipulate a pac4j session cookie. This issue affects Apache Druid versions 0.18.0 through 30.0.0. Since the druid-pac4j extension is optional and disabled by default, Druid installations not using the druid-pac4j extension are not affected by this vulnerability. While we are not aware of a way to meaningfully exploit this flaw, we nevertheless recommend upgrading to version 30.0.1 or higher which fixes the issue and ensuring you have a strong druid.auth.pac4j.cookiePassphrase as a precaution.

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

A Padding Oracle vulnerability exists in Apache Druid's optional druid-pac4j extension (versions 0.18.0-30.0.0), allowing attackers to potentially manipulate the pac4j session cookie. The flaw stems from improper handling of cryptographic padding in the authentication mechanism.

MitigationUpgrade Apache Druid to version 30.0.1 or higher and verify/configure a strong druid.auth.pac4j.cookiePassphrase. If the druid-pac4j extension is unused, it can remain disabled.

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:>= 0.18.0, < 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Verify if druid-pac4j extension is enabled
    Check your Druid extension configuration (common locations: conf/druid/extensions.list or runtime.properties) to see if druid-pac4j is listed among loaded extensions
    Affected if druid-pac4j appears in the enabled extensions list
  2. Determine installed Apache Druid version
    Run 'java -jar druid.jar --version' or check the version file in your Druid installation directory, or look for version information in the startup logs
    Affected if the version is 0.18.0 through 30.0.0 inclusive
  3. Confirm pac4j authentication is actively configured
    Inspect your authentication configuration (common files: conf/druid/authentication-chain.json or runtime.properties with druid.auth.* settings) to verify pac4j authenticator is defined and enabled
    Affected if pac4j-based authentication is present in the authentication chain or configured as an authenticator
  4. Check if session cookie encryption is in use
    Review your configuration for druid.auth.pac4j.cookiePassphrase setting or similar cookie encryption parameters in your runtime.properties or authentication config
    Affected if a cookie-based session (pac4j session cookie) is configured and the extension is loaded

You are affected if druid-pac4j extension is enabled, your Druid version is between 0.18.0 and 30.0.0, and pac4j session cookie authentication is actively configured.

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 higher and verify/configure a strong druid.auth.pac4j.cookiePassphrase. If the druid-pac4j extension is unused, it can remain disabled.

Recommended fix High confidence

30.0.1

  1. Upgrade Apache Druid to version 30.0.1 or higher
  2. After upgrading, verify or set a strong value for druid.auth.pac4j.cookiePassphrase in your configuration as an additional precaution

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

Fix this in Druid Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-45384 — 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-45384 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