CVE-2024-29213
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 < version 2024.2 allows authenticated users on the local machine to run code with elevated privileges due to insecure ACL via unspecified attack vector.
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 versions before 2024.2 contain an insecure Access Control List (ACL) vulnerability that allows authenticated local users to escalate privileges and execute arbitrary code with elevated (SYSTEM) permissions. This is a local privilege escalation flaw requiring prior local authentication.
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< 2024.2CVSS 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 if Ivanti DSM is installedLook for Ivanti Desktop & Server Management in Add/Remove Programs (Windows) or check Program Files for an Ivanti folderAffected if Ivanti DSM is installed on the system
-
Identify installed Ivanti DSM versionCheck the software version through the Windows registry (HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{DisplayName}), or right-click the DSM executable and select Properties > Details, or use: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Ivanti*DSM*'} | Select-Object DisplayName, DisplayVersionAffected if The displayed version is any build earlier than 2024.2
-
Verify service account privilegesOpen Services, find any Ivanti DSM-related services, right-click and select Properties, then check the 'Log on as' account. Also run: Get-Service | Where-Object {$_.DisplayName -like '*Ivanti*'} | Select-Object Name, Status, StartTypeAffected if The service runs under the SYSTEM (Local System) account or another highly privileged account
-
Audit local user accountsRun 'net user' to list local users, and 'net localgroup Administrators' to see who has admin rights. Check if non-admin local users exist who could potentially exploit this LPE flawAffected if There are authenticated local users on the system beyond the administrator account
If Ivanti DSM is installed with a version lower than 2024.2 and runs as a privileged service, the environment is affected by this local privilege escalation vulnerability.
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 · scoped2024.2
Upgrade Ivanti DSM to version 2024.2 or later to remediate the insecure ACL configuration. Review user permissions and audit local user accounts as a defensive measure.
Ivanti DSM 2024.2
- Verify current Ivanti DSM version by checking the installed software or contacting your administrator
- Download Ivanti DSM version 2024.2 or later from the official Ivanti portal or through your licensed distribution channel
- Schedule a maintenance window to apply the update
- Apply the upgrade following standard Ivanti DSM upgrade procedures
- Verify the upgrade was successful and the version is 2024.2 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29213 — 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-2024-29213 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