dbcve.org
Command InjectionWeakness · CWE-77

CVE-2024-54660

HIGH · 8.7 CVSS v3.1 Published 2025-01-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable

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
A JNDI injection issue was discovered in Cloudera JDBC Connector for Hive before 2.6.26 and JDBC Connector for Impala before 2.6.35. Attackers can inject malicious parameters into the JDBC URL, triggering JNDI injection during the process when the JDBC Driver uses this URL to connect to the database. This could lead to remote code execution. JNDI injection is possible via the JDBC connection property krbJAASFile for the Java Authentication and Authorization Service (JAAS). Using untrusted parameters in the krbJAASFile and/or remote host can trigger JNDI injection in the JDBC URL through the krbJAASFile.

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

This is a JNDI injection vulnerability in Cloudera JDBC Connectors for Hive and Impala. Attackers can inject malicious JNDI references through the krbJAASFile JDBC connection property, causing the driver to perform unsafe lookups that can lead to remote code execution. The vulnerability stems from the driver trusting and processing unvalidated JAAS configuration file paths from the JDBC URL.

MitigationUpgrade to Cloudera JDBC Connector for Hive version 2.6.26 or later, and JDBC Connector for Impala version 2.6.35 or later. If immediate patching is not possible, implement network-level controls to restrict outbound LDAP/RMI connections from database servers and validate that krbJAASFile parameters conform to expected patterns.

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

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
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/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 Cloudera JDBC Connectors
    Search for JDBC driver JAR files containing 'Cloudera' and 'Hive' or 'Impala' in the application filesystem, typically in lib directories, JDBC driver folders, or application classpaths
    Affected if Cloudera JDBC Connector for Hive or Impala JAR files are found on the system
  2. Determine the exact version of the installed connector
    Inspect the JAR manifest file (META-INF/MANIFEST.MF) inside the Cloudera JDBC JAR for the Implementation-Version or Specification-Version attribute, or use 'jar -xf' to extract and read the manifest
    Affected if Version is below 2.6.26 for Hive connector or below 2.6.35 for Impala connector
  3. Review JDBC connection configurations for krbJAASFile usage
    Search configuration files, connection strings, and application code for JDBC URLs containing the 'krbJAASFile' parameter
    Affected if The krbJAASFile parameter is present in any JDBC connection string or configuration
  4. Inspect JAAS configuration files referenced by krbJAASFile
    Locate and examine the JAAS configuration file path specified by krbJAASFile; verify the file exists and review its contents for any external JNDI references or suspicious LDAP/RMI endpoints
    Affected if The JAAS configuration file contains references to external LDAP or RMI endpoints, or if the krbJAASFile parameter points to an untrusted or user-controlled location

A user is affected if they have Cloudera JDBC Connector for Hive version below 2.6.26 or Impala version below 2.6.35 AND use the krbJAASFile parameter in their JDBC connection strings, as this combination enables the JNDI injection vector.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Cloudera JDBC Connector for Hive version 2.6.26 or later, and JDBC Connector for Impala version 2.6.35 or later. If immediate patching is not possible, implement network-level controls to restrict outbound LDAP/RMI connections from database servers and validate that krbJAASFile parameters conform to expected patterns.

Recommended fix Moderate confidence

Cloudera JDBC Connector for Hive 2.6.26+ and JDBC Connector for Impala 2.6.35+

  1. Identify the currently installed Cloudera JDBC Connector version (for both Hive and Impala) in your environment
  2. For Cloudera JDBC Connector for Hive: upgrade to version 2.6.26 or later
  3. For Cloudera JDBC Connector for Impala: upgrade to version 2.6.35 or later
  4. Obtain the updated JAR files from the official Cloudera distribution or Maven repository
  5. Replace the existing JDBC connector JAR files in your application libraries
  6. Restart any applications or services that use the JDBC connectors
  7. Verify the upgrade was successful by checking the driver version
Caveat Review release notes for any API or configuration changes between your current version and the fixed version

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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