First published: Thu Jan 16 2025(Updated: )
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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Cloudera JDBC Connector for Hive | <2.6.26 | |
Cloudera JDBC Connector for Impala | <2.6.35 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-54660 is classified as a high severity vulnerability due to the potential for JNDI injection attacks.
To fix CVE-2024-54660, upgrade to Cloudera JDBC Connector for Hive version 2.6.26 or later, or Cloudera JDBC Connector for Impala version 2.6.35 or later.
CVE-2024-54660 affects Cloudera JDBC Connector for Hive versions prior to 2.6.26 and Cloudera JDBC Connector for Impala versions prior to 2.6.35.
The impact of CVE-2024-54660 includes potential unauthorized access to resources via JNDI injection, compromising database integrity and security.
There are currently no documented workarounds for CVE-2024-54660; upgrading to the secure versions is strongly recommended.