CVE-2023-27323
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 · uneditedParallels Desktop Updater Time-Of-Check Time-Of-Use Local Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of Parallels Desktop. An attacker must first obtain the ability to execute low-privileged code on the target host system in order to exploit this vulnerability. The specific flaw exists within the Updater service. By creating a symbolic link, an attacker can abuse the service to execute a file. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of root. . Was ZDI-CAN-18150.
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 confidenceThis is a Time-Of-Check Time-Of-Use (TOCTOU) vulnerability in the Parallels Desktop Updater service. A local attacker with low-privileged code execution can create a symbolic link to abuse a race condition between file validation and file execution in the updater, leading to arbitrary code execution with root 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< 18.1.0_\(53311\)CVSS 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.0/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 Parallels Desktop installed versionOpen Terminal and run: `defaults read /Applications/Parallels\ Desktop.app/Contents/Info.plist CFBundleVersion` or check via Parallels Desktop menu: Parallels Desktop > About Parallels DesktopAffected if Installed version is less than 18.1.0 (build 53311)
-
Verify Updater service existsCheck for the presence of the updater component: `ls -la /Library/Application\ Support/Parallels/Parallels\ Updater.app` or look for prl_updater processes running: `ps aux | grep -i updater`Affected if Updater service is present on the system
-
Check updater directory permissionsExamine write permissions on updater directories: `ls -la /Library/Application\ Support/Parallels/` and `ls -la /Library/Application\ Support/Parallels/Parallels\ Updater.app/Contents/MacOS/`Affected if Low-privileged users can write to updater directories or create symbolic links in them
-
Detect existing symbolic links in updater pathsSearch for symbolic links in updater-related paths: `find /Library/Application\ Support/Parallels -type l -ls 2>/dev/null`Affected if Any unexpected symbolic links exist in Parallels updater directories
-
Confirm low-privileged user accessVerify the attacking user has code execution capability: check if standard user accounts exist on the system and can run commandsAffected if Standard non-root users have shell access to the system
The system is affected if Parallels Desktop version is below 18.1.0 (build 53311) AND the Updater service is installed AND low-privileged users can create symbolic links in updater directories.
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 · scoped18.1.0_
Apply the vendor security update for Parallels Desktop when available. Until then, restrict user access to the updater service and monitor for suspicious symbolic link creation in updater directories.
Parallels Desktop 18.1.0 (build 53311) or later
- Check the current Parallels Desktop version by going to Parallels Desktop menu > About Parallels Desktop
- Navigate to the official Parallels download page or use Parallels Check for Updates within the application
- Download Parallels Desktop version 18.1.0 (build 53311) or later
- Install the update following the on-screen prompts
- Restart the virtual machine or the host system if prompted by the installer
- Verify the installed version is 18.1.0_(53311) or higher via About Parallels Desktop
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-27323 — 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-27323 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