CVE-2021-3162
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 Community before 2.5.0.0 on macOS mishandles certificate checking, leading to local privilege escalation.
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 Community versions prior to 2.5.0.0 on macOS contain a vulnerability in certificate validation logic. This flaw allows an authenticated local user to escalate privileges by exploiting improper certificate checking, potentially executing code or gaining elevated access on the affected system.
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< 2.5.0.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.
-
Verify Docker Desktop is installed on macOSRun 'ls /Applications | grep -i docker' or check for Docker.app in /Applications folder. Alternatively, run 'docker --version' to see if Docker CLI can connect to a Docker Desktop instance.Affected if Docker Desktop is not found in Applications or Docker CLI returns no output indicating no running Docker Desktop instance
-
Check the installed Docker Desktop versionOn macOS, open Docker Desktop and go to 'Docker Desktop' menu > 'About Docker Desktop' to view the version number. Alternatively, run: 'defaults read /Applications/Docker.app/Contents/Info.plist CFBundleShortVersionString' or check '~/Library/Application Support/Docker/Docker Desktop.plist' for the version key.Affected if The displayed version is any version prior to 2.5.0.0 (e.g., 2.4.0.0, 2.3.0.3, etc.)
-
Confirm the platform is macOSRun 'uname -s' and verify the output is 'Darwin', or check System Preferences > About > System Report > Software > macOS version.Affected if The operating system is macOS and the Docker Desktop version is below 2.5.0.0
You are affected if Docker Desktop Community is installed on macOS and the installed version is lower than 2.5.0.0.
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.
From vendor data2.5.0.0
Upgrade Docker Desktop Community to version 2.5.0.0 or later on macOS systems. This is a local privilege escalation vulnerability requiring authenticated local access.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-3162 — 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-2021-3162 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