CVE-2022-27088
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 · uneditedIvanti DSM Remote <= 6.3.1.1862 is vulnerable to an unquoted service path allowing local users to launch processes with elevated privileges.
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 confidenceIvanti DSM Remote <= 6.3.1.1862 contains an unquoted service path vulnerability where the Windows service executable path lacks proper quoting. Local attackers can place malicious executables in intermediate path directories, which Windows will attempt to execute with elevated privileges when the service starts.
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<= 6.3.1.1862CVSS 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.
-
Identify Ivanti DSM Remote installation and versionOpen Windows Registry and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or check Program Files for Ivanti DSM folder. Look for a version entry or check the executable properties of the DSM Remote service binary.Affected if The installed version is 6.3.1.1862 or lower.
-
Locate the Ivanti DSM Remote Windows serviceOpen Services (services.msc) and locate the Ivanti DSM Remote service, or query from command line: sc queryex type= service state= all | findstr /i "dsm"Affected if No Ivanti DSM Remote service is found, meaning the product may not be installed or uses a different service name.
-
Examine the service executable path configurationRun the command: sc qc "Ivanti DSM Remote Service" (replace with actual service name found). This displays the BINARY_PATH_NAME which is the service executable path.Affected if The BINARY_PATH_NAME field shows a path without quotation marks around it, such as: C:\Program Files\Ivanti\DSM\bin\Remote.exe /service
-
Check permissions on intermediate path directoriesFor each directory in the unquoted path (e.g., C:\Program Files\Ivanti\DSM\bin), right-click the folder in Windows Explorer, go to Properties > Security, and verify which users have Write or Execute permissions. From command line, use: icacls "C:\Program Files\Ivanti\DSM\bin"Affected if Standard users or the attacker-controlled account has Write or Write+Execute permissions to any directory in the path before the executable name.
The environment is affected if Ivanti DSM Remote version is 6.3.1.1862 or lower AND the service BINARY_PATH_NAME is unquoted, allowing an attacker to place a malicious executable in a writable intermediate directory.
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 dataApply the vendor patch for Ivanti DSM Remote to properly quote the service executable path, or manually correct the service configuration in the Windows registry to enclose the path in quotation marks.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27088 — 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-2022-27088 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