Docker DesktopApplication · Docker
CVE-2023-5166
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 · uneditedDocker Desktop before 4.23.0 allows Access Token theft via a crafted extension icon URL. This issue affects Docker Desktop: before 4.23.0.
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 · moderate confidenceDocker Desktop before version 4.23.0 contains a vulnerability where crafted extension icon URLs can be leveraged to steal access tokens. This suggests improper validation or sanitization of extension icon URL parameters, allowing an attacker to potentially intercept or redirect authentication credentials.
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
Docker DesktopApplication
< 4.23.0CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Check Docker Desktop installed versionOpen Docker Desktop, click the gear icon to access Settings, then go to 'About Docker Desktop' to view the version number. Alternatively, run 'docker --version' in a terminal.Affected if The displayed version is any version before 4.23.0 (e.g., 4.22.0, 4.20.0, etc.)
-
Verify Docker Desktop extensions are enabledOpen Docker Desktop Settings and navigate to the 'Extensions' section. Check if extensions are enabled or if any extensions are installed.Affected if Extensions are enabled or any third-party extensions are installed, and the Docker Desktop version is below 4.23.0
-
Inspect extension configuration filesOn Windows, check %APPDATA%\Docker\extensions\settings.json. On macOS, check ~/Library/Group\ Containers/group.com.docker/settings.json. Look for any custom extension entries with icon URL fields.Affected if Custom extension icon URLs are configured and the Docker Desktop version is below 4.23.0
A user is affected if Docker Desktop version is below 4.23.0 and extensions (especially with custom icon URLs) are enabled or configured.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.23.0
Upgrade Docker Desktop to version 4.23.0 or later to remediate this vulnerability.
Docker Desktop 4.23.0
- Check current Docker Desktop version by clicking the Docker icon in the system tray and selecting 'About Docker Desktop'
- Download Docker Desktop version 4.23.0 or later from the official Docker website (docker.com/products/docker-desktop)
- Run the installer and follow the prompts to complete the upgrade
- Restart Docker Desktop after the installation completes
- Verify the upgrade was successful by checking the version again in 'About Docker Desktop'
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Docker Desktop
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-5166 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-5166 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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