# CVE-2024-6507: Deep Lake Kaggle command injection

> Attackers can execute arbitrary commands via unsanitized input in the Kaggle dataset ingestion API of the Deep Lake library.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jul 2024
- **Updated:** 25 Nov 2024
- **Also known as:** GHSA-c6gx-2rc7-2pg3

## What is CVE-2024-6507?

CVE-2024-6507 is a high-severity command injection vulnerability, published on 4 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Command injection when ingesting a remote Kaggle dataset due to a lack of input sanitization in the ingest_kaggle() API

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2024-6507 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-6507 is a high-severity command injection vulnerability, published on 4 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6507 exists.

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-6507/ (Markdown: https://insights.sbomify.com/CVE-2024-6507/index.md)
```

## Sources

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

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