dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2024-9348

HIGH · 8.9 CVSS v4.0 Published 2024-10-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Docker Desktop versions before v4.34.3 contain a Remote Code Execution (RCE) vulnerability in the Build view component. The vulnerability stems from insufficient sanitization of GitHub source links, allowing attackers to inject and execute arbitrary code by tricking users into interacting with malicious links.

MitigationUpgrade Docker Desktop to version v4.34.3 or later to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
Authentication
X
User interaction
A
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Docker Desktop version
    Open Docker Desktop and navigate to the Docker Desktop menu (click the Docker icon in the system tray or menu bar), then select 'About Docker Desktop' to view the installed version number
    Affected if The displayed version is earlier than v4.34.3 (e.g., v4.34.2, v4.34.1, v4.34.0, or any earlier version)
  2. Identify Build view usage
    In Docker Desktop, locate the Build view component. This is typically found in the Docker Desktop UI under the Build or BuildKit section where users can configure and execute container image builds
    Affected if The Build view feature is present and accessible in the Docker Desktop installation
  3. Determine if GitHub source links are used
    Within the Build view, check if there are options to import or reference GitHub repositories as build sources. Look for fields or buttons that allow specifying a GitHub URL as the source for a build
    Affected if Users have access to or use the GitHub source link functionality within the Build view to import external repositories

A user is affected if they are running Docker Desktop versions earlier than v4.34.3 AND have access to the Build view component with GitHub source link functionality enabled or in use

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Docker Desktop to version v4.34.3 or later to remediate this vulnerability.

Recommended fix High confidence

Docker Desktop v4.34.3 or later

  1. Open Docker Desktop
  2. Click on the Docker Desktop menu (whale icon in system tray)
  3. Select 'Check for Updates' or navigate to Settings > General
  4. If an update is available, click 'Update' to download and install Docker Desktop v4.34.3 or later
  5. Restart Docker Desktop after the update completes
  6. Verify the installed version by going to Docker Desktop menu > 'About Docker Desktop' and confirming the version is v4.34.3 or higher
Caveat Review Docker Desktop release notes for v4.34.3 for any compatibility or feature changes before updating

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-9348 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-9348 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data