dbcve.org
DesktopApplication · Docker

CVE-2024-8695

CRITICAL · 9.8 CVSS v3.1 Published 2024-09-12
Fix available
A fix is available. Upgrade to 4.34.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
A remote code execution (RCE) vulnerability via crafted extension description/changelog could be abused by a malicious extension in Docker Desktop before 4.34.2.

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

A remote code execution (RCE) vulnerability in Docker Desktop versions before 4.34.2 allows a malicious extension to execute arbitrary code by embedding malicious payloads in crafted extension description or changelog fields. The CVSS 9.8 score indicates trivial network exploitability with complete system compromise potential.

MitigationUpgrade Docker Desktop to version 4.34.2 or later to remediate this vulnerability. Organizations should also review and audit installed extensions for any malicious extensions already present.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DesktopApplication
Affected:< 4.34.2

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Verify Docker Desktop is installed
    On Windows, check C:\Program Files\Docker\Docker\Docker Desktop.exe. On macOS, check /Applications/Docker.app. Alternatively, run 'docker version' or 'docker-desktop --version' from command line.
    Affected if Docker Desktop is not found on the system, the vulnerability does not apply.
  2. Determine the installed Docker Desktop version
    Run 'docker --version' or 'docker-desktop --version' in command line. On Windows, right-click Docker Desktop.exe and select Properties > Details to view File Version. On macOS, right-click Docker.app in Applications > Get Info to see Version.
    Affected if Unable to determine version indicates Docker Desktop may not be installed.
  3. Compare installed version against affected range
    Compare the version number found in step 2 to 4.34.2. Note that version numbers follow semver format. Versions before 4.34.2 (such as 4.34.1, 4.34.0, 4.33.0, etc.) are affected.
    Affected if Installed version is lower than 4.34.2 (for example, 4.34.1, 4.33.0, or any 4.x version below 4.34.2).
  4. Check if Docker Extensions are enabled or in use
    Open Docker Desktop, go to the Extensions tab in Settings, or run 'docker extension ls' if CLI plugin is available. Review installed extensions and their descriptions/changelogs.
    Affected if Extensions with untrusted or unknown sources are installed, and the version is below 4.34.2, the attack vector is present.

User is affected if Docker Desktop version is installed and is lower than 4.34.2, with Docker extensions enabled or installed.

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
Upgrade available Upgrade to 4.34.2 or later
Fixed in 4.34.2
Interim mitigation

Upgrade Docker Desktop to version 4.34.2 or later to remediate this vulnerability. Organizations should also review and audit installed extensions for any malicious extensions already present.

Recommended fix High confidence

Docker Desktop 4.34.2

  1. Back up any important Docker volumes or data as a precautionary measure
  2. Stop any running Docker Desktop instance
  3. Download Docker Desktop version 4.34.2 or later from the official Docker website (docker.com)
  4. Run the Docker Desktop installer for the new version
  5. Follow the on-screen installation prompts
  6. Start Docker Desktop after installation completes
  7. Verify the Docker Desktop version is 4.34.2 or later by checking the About Docker Desktop section

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

Fix this in Desktop Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8695 — 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-8695 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