CVE-2024-7572
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 · uneditedInsufficient permissions in Ivanti DSM before version 2024.3.5740 allows a local authenticated attacker to delete arbitrary files.
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 confidenceInsufficient permission controls in Ivanti DSM before version 2024.3.5740 allow a local authenticated attacker to delete arbitrary files on the system due to missing authorization checks on file deletion operations.
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.2, < 2024.3.5740CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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 installed Ivanti DSM versionLocate the Ivanti Desktop & Server Management installation and retrieve its version number. This is typically found in the application properties, about dialog, or installation directory. On Windows, you may also find version information in the Windows Registry under the Ivanti product keys, or by running 'Get-ItemProperty' on the installation folder.Affected if The installed version is 2024.2 or any version between 2024.2 and 2024.3.5739 (inclusive)
-
Confirm version falls within vulnerable rangeCompare the identified version number against the affected range: greater than or equal to 2024.2, and less than 2024.3.5740Affected if The version meets both conditions: it is 2024.2 or newer, but older than 2024.3.5740
-
Verify local authentication is enabledConfirm that local user authentication to the Ivanti DSM system is possible. Check if local Windows accounts or domain accounts can authenticate to the Ivanti DSM console or related services.Affected if Local or domain user accounts can authenticate to the Ivanti DSM environment
-
Check for file deletion operation availabilityDetermine if file deletion functionality is exposed through Ivanti DSM. This may include DSM policies, script execution features, or administrative tools that allow file operations.Affected if File deletion operations are accessible through Ivanti DSM features such as policies, scripts, or administrative tools
You are affected if Ivanti DSM version 2024.2 or later but earlier than 2024.3.5740 is installed and local authenticated access or file deletion features are available in your environment.
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.3.5740
Upgrade Ivanti DSM to version 2024.3.5740 or later to remediate the insufficient permission vulnerability. Restrict local administrative access until the patch is applied.
2024.3.5740 or later
- Verify current Ivanti DSM version by checking the About or version information in the management console
- Download Ivanti DSM version 2024.3.5740 or later from the official Ivanti download portal or support site
- Review Ivanti DSM 2024.3.5740 release notes for any prerequisites or migration considerations
- Create a full backup of the Ivanti DSM database and configuration
- Schedule a maintenance window to minimize business impact
- Stop all Ivanti DSM services before beginning the upgrade
- Run the installer for version 2024.3.5740 or later
- Follow the on-screen upgrade wizard instructions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-7572 — 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-7572 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