CVE-2021-31420
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 · uneditedThis vulnerability allows local attackers to escalate privileges on affected installations of Parallels Desktop 16.1.0-48950. An attacker must first obtain the ability to execute low-privileged code on the target guest system in order to exploit this vulnerability. The specific flaw exists within the Toolgate component. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of the hypervisor. Was ZDI-CAN-12220.
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 confidenceA stack-based buffer overflow in the Toolgate component of Parallels Desktop 16.1.0-48950 allows local attackers who can execute low-privileged code on the guest VM to overflow a stack buffer by failing to validate the length of user-supplied data before copying, leading to hypervisor-level code execution and privilege escalation.
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= 16.1.0-48950CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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 Parallels Desktop is installedOn the macOS host, check for the presence of Parallels Desktop application in /Applications or via system_profiler SPApplicationsByType commandAffected if Parallels Desktop is not installed on the system
-
Determine installed Parallels Desktop versionOpen Parallels Desktop, go to Parallels Desktop menu > About Parallels Desktop, or run: defaults read /Applications/Parallels\ Desktop.app/Contents/Info.plist CFBundleVersionAffected if Version displayed does not match 16.1.0-48950 exactly
-
Confirm guest VMs are in useCheck if any guest virtual machines are configured in Parallels Desktop by examining ~/Library/Parallels/ or the Parallels Desktop VM listAffected if Guest VMs exist and the Toolgate component is active between guest and host
-
Check for code execution capability in guestVerify whether untrusted or low-privileged code can execute within any guest VM by reviewing VM configurations and installed software within guestsAffected if Low-privileged or untrusted code execution is possible inside any guest VM
You are affected only if Parallels Desktop version 16.1.0-48950 is installed and you run guest VMs where an attacker could execute code to trigger the Toolgate buffer overflow.
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 · scopedApply the vendor security update for Parallels Desktop; restrict execution of untrusted code within guest VMs to reduce attack surface.
Latest Parallels Desktop 16.x or newer version with security fix (verify current fixed release at kb.parallels.com)
- Verify the currently installed Parallels Desktop version by going to Parallels Desktop menu > About Parallels Desktop
- Navigate to the official Parallels knowledge base at kb.parallels.com to check for security updates related to CVE-2021-31420
- Download and install the latest available version of Parallels Desktop that includes the security fix for this vulnerability
- After updating, verify the installation by checking the version number in About Parallels Desktop matches the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-31420 — 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-31420 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