CVE-2024-54660
Published: 16 January 2025
Summary
CVE-2024-54660 is a high-severity Command Injection (CWE-77) vulnerability in Blackhat (inferred from references). Its CVSS base score is 8.7 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 25.0% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified are NIST 800-53 SI-10 (Information Input Validation) and SI-2 (Flaw Remediation).
Deeper analysis
CVE-2024-54660 is a JNDI injection vulnerability in Cloudera JDBC Connector for Hive versions before 2.6.26 and JDBC Connector for Impala versions before 2.6.35. The flaw enables attackers to inject malicious parameters into the JDBC URL, which triggers JNDI injection during database connection attempts by the JDBC driver. Exploitation occurs via the JDBC connection property krbJAASFile for Java Authentication and Authorization Service (JAAS), where untrusted parameters in krbJAASFile or a remote host can lead to remote code execution.
Attackers with network access can exploit this vulnerability with low attack complexity, requiring low privileges (PR:L) and user interaction (UI:R). Upon success, it results in high confidentiality and integrity impacts (C:H/I:H) with a changed scope (S:C), yielding a CVSS v3.1 base score of 8.7 (CWE-77). This allows remote code execution on the victim's system attempting the database connection.
The referenced Black Hat EU-24 briefing details a novel attack surface in JAAS, highlighting the vulnerability's mechanics. Mitigation requires upgrading to Cloudera JDBC Connector for Hive 2.6.26 or later and Impala 2.6.35 or later to address the JNDI injection risk.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-52643
Vulnerability details
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
JNDI injection in JDBC driver enables RCE via malicious connection parameters (network-accessible, low complexity).
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Requires timely remediation of flaws through vendor patches, directly addressing the JNDI injection vulnerability by upgrading to fixed Cloudera JDBC Connector versions.
Mandates validation of untrusted information inputs like JDBC URL parameters, preventing JNDI injection via malicious krbJAASFile properties.
Establishes secure configuration settings for JDBC drivers to restrict or sanitize risky connection properties like krbJAASFile, mitigating injection risks.