dbcve.org
Desktop \& Server ManagementApplication · Ivanti

CVE-2023-28129

HIGH · 7.8 CVSS v3.1 Published 2023-08-10
Fix available
A fix is available. Upgrade to 2022.2 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
DSM 2022.2 SU2 and all prior versions allows a local low privileged account to execute arbitrary OS commands as the DSM software installation user.

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 confidence

This is a local privilege escalation vulnerability in DSM (Dassault Systèmes SIMULIA) software. A user with low-privileged local account access can execute arbitrary operating system commands in the context of the DSM software installation user account, effectively gaining elevated privileges on the system.

MitigationApply the vendor patch from Dassault Systèmes for DSM 2022.2 SU2 or later. In the interim, limit local system access to trusted personnel only and monitor for suspicious command execution.

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
Desktop \& Server ManagementApplication
Affected:< 2022.2= 2022.2

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.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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Ivanti Desktop & Server Management is installed
    Check the system for the presence of Ivanti Desktop & Server Management software. This may be visible in installed programs list, program files directory, or running services. Look for DSM-related services or the SIMULIA DSM application.
    Affected if The software is present on the system and is a version listed in the affected versions below.
  2. Determine the installed version of the software
    Locate the version information for the installed Ivanti Desktop & Server Management or DSM software. This is typically found in the software's About dialog, an installed version file, or via command-line version query if available.
    Affected if The installed version is either lower than 2022.2, or exactly 2022.2.
  3. Verify the DSM service account privileges
    Check the user account context under which the DSM or Ivanti Desktop & Server Management service runs. This can be done by examining service configuration in the system service management console or via command-line tools.
    Affected if The service runs under a privileged account (such as an administrator or a user with elevated system access) and low-privileged local users have access to interact with this service.
  4. Assess local user access controls
    Review which local user accounts exist on the system and their membership levels. Check if untrusted or low-privileged local accounts have any ability to interact with DSM-related processes or configurations.
    Affected if Low-privileged local user accounts exist and have any potential pathway to trigger command execution through the vulnerable DSM functionality.

A user is affected if Ivanti Desktop & Server Management or DSM software is installed with version 2022.2 or lower, and low-privileged local accounts can potentially interact with the software's service or functionality to escalate privileges.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2022.2 or later
Fixed in 2022.2
Interim mitigation

Apply the vendor patch from Dassault Systèmes for DSM 2022.2 SU2 or later. In the interim, limit local system access to trusted personnel only and monitor for suspicious command execution.

Recommended fix Moderate confidence

Ivanti DSM 2022.2 Service Update 2 (SU2) or later

  1. 1. Identify the current installed version of Ivanti DSM (Desktop & Server Management)
  2. 2. Navigate to the Ivanti customer portal or download center
  3. 3. Download Ivanti DSM version 2022.2 Service Update 2 (SU2) or later
  4. 4. Review the release notes for any prerequisites or special installation instructions
  5. 5. Create a full backup of the DSM database and configuration
  6. 6. Test the upgrade in a non-production environment first
  7. 7. Apply the upgrade during a planned maintenance window
  8. 8. Verify the installation was successful and the service is running
Caveat Review release notes for any configuration changes or deprecated features that may require adjustment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Desktop \& Server Management Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-28129 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-28129 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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