# CVE-2024-54660: Code injection in n/a

> Attackers can achieve remote code execution by injecting malicious JNDI parameters into the JDBC connection URL via the krbJAASFile property.

- **Severity:** High 8.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Jan 2025
- **Updated:** 3 Feb 2025
- **Also known as:** GHSA-5pc4-8q9w-w6v9

## What is CVE-2024-54660?

CVE-2024-54660 is a high-severity code injection vulnerability in n/a, published on 16 Jan 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2024-54660?


## How do I fix CVE-2024-54660?

No fix has been published for CVE-2024-54660 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-54660 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-54660 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-54660 and fix it if it is affected.

What it is: CVE-2024-54660 is a high-severity code injection vulnerability in n/a, published on 16 Jan 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-54660 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-54660/ (Markdown: https://insights.sbomify.com/CVE-2024-54660/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-54660
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-54660
- OSV: https://osv.dev/vulnerability/CVE-2024-54660

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-54660/
Summaries are generated and may contain mistakes; the official description above is the record.