CVE-2021-31425
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.2-49151. 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 Parallels Tools component. The issue results from the lack of proper validation of user-supplied data, which can result in an integer overflow before allocating a buffer. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of the kernel on the target guest system. Was ZDI-CAN-12790.
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 confidenceLocal privilege escalation vulnerability in Parallels Desktop's Parallels Tools component. The flaw stems from insufficient validation of user-supplied data that can trigger an integer overflow before buffer allocation, allowing an attacker with initial low-privileged code execution to escalate to kernel-level privileges within the guest 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= 16.1.2-49151CVSS 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.
-
Confirm Parallels Desktop is installedOn the macOS host, check for Parallels Desktop application in /Applications or via System Preferences > Security & Privacy > General to see if it was installed from the App Store. Alternatively, run 'ls /Applications | grep -i parallels' in terminal.Affected if Parallels Desktop is not installed on the system.
-
Identify installed Parallels Desktop versionOpen Parallels Desktop, go to Help > About Parallels Desktop, or run 'prlctl --version' on the macOS host to retrieve the exact version and build number.Affected if The installed version is exactly 16.1.2 build 49151.
-
Verify Parallels Tools is installed in the guest VMWithin the guest operating system (the virtual machine), check if Parallels Tools are installed. On Windows guest: look for Parallels Tools in Add/Remove Programs or check C:\Program Files\Parallels\Parallels Tools. On Linux guest: check /usr/lib/parallels-tools or run 'lsmod | grep prl'Affected if Parallels Tools are installed and running in the guest virtual machine.
-
Assess guest VM execution environmentDetermine whether untrusted or low-privileged code can execute within the guest virtual machine. Review installed software, user permissions, and application execution policies.Affected if Untrusted or low-privileged users can execute code within the guest VM.
A system is affected if Parallels Desktop version 16.1.2-49151 is installed with Parallels Tools enabled in the guest VM and the guest permits execution of untrusted code.
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-supplied patch or update Parallels Desktop to a patched version. Until patched, restrict execution of untrusted code within the guest virtual machine to reduce the attack surface.
Parallels Desktop version later than 16.1.2-49151 (verify fixed release on kb.parallels.com)
- 1. Verify the current Parallels Desktop version by going to Parallels Desktop menu > About Parallels Desktop
- 2. Check Parallels support portal (kb.parallels.com) or the official security advisory for the fixed version addressing CVE-2021-31425
- 3. If a newer version is available, download and install the update
- 4. After upgrading, ensure Parallels Tools are updated to the latest version within the guest虚拟机
- 5. Restart the virtual machine to apply all updates
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.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,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-31425 — 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-31425 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