CVE-2024-29821
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 · high confidenceIvanti DSM versions before 2024.2 contain an insecure Access Control List (ACL) that allows any authenticated user on the local machine to escalate their privileges and execute code with elevated/system-level permissions. This is a local privilege escalation vulnerability 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.
-
Determine installed Ivanti DSM versionLocate the Ivanti DSM installation directory and check the version information, typically found in the product's main executable, about dialog, or installation metadata. Compare the version number to the affected range (versions before 2024.2).Affected if Installed version is earlier than 2024.2
-
Identify Ivanti DSM service account and permissionsUse tools such as 'sc qc' or the Services console to identify the account under which the Ivanti DSM service runs. Then use 'icacls' or equivalent access control listing tools to examine the permissions granted to authenticated users on the service executable and related binaries.Affected if Authenticated local users have write or modify permissions on service binaries or configuration files
-
Review ACLs on Ivanti DSM installation directoryExecute 'icacls <installation_path>' on the Ivanti DSM root directory and subdirectories. Examine the access control entries for groups such as 'Users', 'Authenticated Users', or 'Everyone' to determine if non-privileged users have excessive permissions.Affected if Non-admin users have write, modify, or full control permissions on critical application directories or files
-
Check for weak service file permissionsInspect permissions on executable files associated with Ivanti DSM services using 'icacls' or Get-Acl PowerShell cmdlets. Verify that only Administrators and SYSTEM have write access to these files.Affected if Service executable files are writable by standard authenticated users
The environment is affected if Ivanti DSM version is below 2024.2 AND authenticated local users possess write or modify permissions on service executables, installation directories, or configuration files that should be restricted to administrators.
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 apply the vendor patch that remediates the insecure ACL configuration.
2024.2 or later
- 1. Back up the current Ivanti DSM configuration and database before beginning the upgrade process
- 2. Obtain Ivanti DSM version 2024.2 or later from the official Ivanti download portal or support site
- 3. Review the 2024.2 release notes for any specific upgrade prerequisites or migration requirements
- 4. Execute the installer/upgrader following Ivanti's standard upgrade procedure for DSM
- 5. Verify the upgrade completed successfully and ACL permissions are now correctly configured
- 6. Validate that the vulnerability is remediated by confirming local authenticated users can no longer elevate privileges
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29821 — 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-29821 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