CVE-2025-34352
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 · uneditedJumpCloud Remote Assist for Windows versions prior to 0.317.0 include an uninstaller that is invoked by the JumpCloud Windows Agent as NT AUTHORITY\SYSTEM during agent uninstall or update operations. The Remote Assist uninstaller performs privileged create, write, execute, and delete actions on predictable files inside a user-writable %TEMP% subdirectory without validating that the directory is trusted or resetting its ACLs when it already exists. A local, low-privileged attacker can pre-create the directory with weak permissions and leverage mount-point or symbolic-link redirection to (a) coerce arbitrary file writes to protected locations, leading to denial of service (e.g., by overwriting sensitive system files), or (b) win a race to redirect DeleteFileW() to attacker-chosen targets, enabling arbitrary file or folder deletion and local privilege escalation to SYSTEM. This issue is fixed in JumpCloud Remote Assist 0.317.0 and affects Windows systems where Remote Assist is installed and managed through the Agent lifecycle.
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 confidenceJumpCloud Remote Assist for Windows uninstaller runs as NT AUTHORITY\SYSTEM and performs privileged create, write, execute, and delete operations on predictable files inside a user-writable %TEMP% subdirectory without validating directory trust or resetting ACLs. A local low-privileged attacker can pre-create this directory with weak permissions and use mount-point or symbolic-link redirection to either force arbitrary file writes to protected locations causing DoS, or win a race condition to redirect DeleteFileW() to attacker-chosen targets enabling arbitrary file deletion and LPE to SYSTEM.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 if JumpCloud Remote Assist is installedOpen Programs and Features (appwiz.cpl) or check Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for JumpCloud Remote Assist entryAffected if The product is not listed or no uninstall entry exists - not affected. If present, continue to version check.
-
Determine installed version of JumpCloud Remote AssistIn Programs and Features, locate JumpCloud Remote Assist and note the Version column, or query the registry Uninstall key for the DisplayVersion valueAffected if Version displayed is below 0.317.0 - system is affected. Version 0.317.0 or later is not affected.
-
Locate the uninstaller binaryCheck the installation directory (typically C:\Program Files\JumpCloud\ or C:\Program Files (x86)\JumpCloud\) for an uninstall executable, or query the registry Uninstall key for the UninstallString valueAffected if If the uninstaller exists and the version from step 2 is below 0.317.0, the vulnerable code path is present.
-
Verify uninstaller runs with elevated privilegesRun the uninstaller while monitoring with Process Explorer or Task Manager to confirm it executes as NT AUTHORITY\SYSTEMAffected if Uninstaller runs as SYSTEM and version is below 0.317.0 - the privilege escalation condition exists.
If JumpCloud Remote Assist version is present and below 0.317.0, the environment is affected by this vulnerability where the SYSTEM-privileged uninstaller can be manipulated via temp directory symlinks.
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 · scopedUpgrade JumpCloud Remote Assist to version 0.317.0 or later. In the interim, restrict write access to %TEMP% subdirectories and monitor for suspicious symlink/mount-point creation in temp folders.
JumpCloud Remote Assist 0.317.0
- Identify all Windows systems with JumpCloud Remote Assist installed using your JumpCloud admin console or asset inventory
- Check the current version of JumpCloud Remote Assist on affected systems (versions prior to 0.317.0 are vulnerable)
- Upgrade JumpCloud Remote Assist to version 0.317.0 or later through the JumpCloud admin console or your chosen deployment method
- Verify the upgrade was successful by confirming the installed version is 0.317.0 or higher
- Ensure the upgrade completes during the agent uninstall or update operation as this is when the vulnerable uninstaller code is invoked
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-2025-34352 — 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-2025-34352 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