Docker DesktopApplication · Docker
CVE-2023-0627
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 4.11.x allows --no-windows-containers flag bypass via IPC response spoofing which may lead to Local Privilege Escalation (LPE).This issue affects Docker Desktop: 4.11.X.
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 4.11.x contains a vulnerability allowing attackers to bypass the --no-windows-containers security flag through IPC response spoofing, enabling local privilege escalation to elevated privileges.
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.11.0, < 4.12.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Docker Desktop versionOpen Docker Desktop and navigate to About Docker Desktop, or run 'docker version' in the terminal to see the version informationAffected if The installed version is 4.11.0, 4.11.1, or any version in the 4.11.x range before 4.12.0
-
Determine if Windows containers feature is enabledCheck Docker Desktop settings by right-clicking the Docker icon in system tray, selecting Settings, then navigating to the General or Containers section to see if Windows containers are enabled or if the --no-windows-containers flag is in useAffected if Windows containers are enabled or the --no-windows-containers flag is being used to block them
-
Verify IPC communication configurationExamine Docker Desktop's IPC mechanism by checking the Docker Desktop settings or logs in the Docker data directory (typically %APPDATA%\Docker on Windows or ~/Library/Containers/com.docker.docker on macOS) for any IPC-related configuration filesAffected if IPC response validation is not properly configured or suspicious IPC responses are logged
A user is affected if Docker Desktop version is 4.11.0 through 4.11.x (before 4.12.0) and the Windows containers feature or the --no-windows-containers security flag is in use, allowing potential IPC response spoofing for privilege escalation.
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.12.0
Update Docker Desktop to a patched version that properly validates IPC responses and prevents the --no-windows-containers flag bypass.
Docker Desktop 4.12.0 or later
- Upgrade Docker Desktop to version 4.12.0 or later to remediate the vulnerability
- Ensure all running containers are stopped before upgrading
- After upgrade, verify the --no-windows-containers flag cannot be bypassed via IPC response spoofing
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Docker Desktop
Scoped from the published advisory
- Consultation3.0 h
- Implementation1.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,264.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0627 — 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-0627 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