# CVE-2024-9348: Docker Desktop before v4.34.3 allows RCE via unsanitized GitHub source link in Build view

> Attackers can execute arbitrary code via unsanitized GitHub source links in the Build view of Docker Desktop.

- **Severity:** High 8.9 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Oct 2024
- **Updated:** 17 Oct 2024
- **Also known as:** GHSA-x6x8-x7qh-52jw

## What is CVE-2024-9348?

CVE-2024-9348 is a high-severity code injection vulnerability in Docker Desktop, published on 16 Oct 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Docker Desktop before v4.34.3 allows RCE via unsanitized GitHub source link in Build view.

Weakness: CWE-116 (Improper Encoding or Escaping of Output), CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2024-9348 being exploited?

There is no known exploitation of CVE-2024-9348 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-9348 is a high-severity code injection vulnerability in Docker Desktop, published on 16 Oct 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-9348 in the wild and no public exploit code.

Affected product: Docker Desktop. 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-9348/ (Markdown: https://insights.sbomify.com/CVE-2024-9348/index.md)
```

## Sources

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

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