dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2024-32840

HIGH · 7.2 CVSS v3.1 Published 2024-09-12
Fix available
A fix is available. Upgrade to 2022 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
An unspecified SQL injection in Ivanti EPM before 2022 SU6, or the 2024 September update allows a remote authenticated attacker with admin privileges to achieve remote code execution.

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 confidence

An SQL injection vulnerability in Ivanti Endpoint Manager (EPM) allows an authenticated remote attacker with admin privileges to execute arbitrary code on the affected system. The vulnerability exists in versions before 2022 SU6 or the 2024 September update.

MitigationApply the vendor-supplied patch: upgrade to Ivanti EPM 2022 SU6 or later, or deploy the 2024 September update. Prior to deployment, verify the current version in the environment and test the update in a non-production environment.

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
Endpoint ManagerApplication
Affected:< 2022= 2022= 2024

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
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Confirm Ivanti Endpoint Manager is installed
    Locate the EPM installation directory (typically C:\Program Files\LANDesk\ or C:\Program Files\Ivanti\), check for core server components, or query Windows Services for 'LANDesk Management' or 'Ivanti Endpoint Manager' services
    Affected if The product is not present on the system
  2. Identify the installed EPM version
    Access the EPM admin console and navigate to Help > About, or check the registry key HKLM\SOFTWARE\LANDesk\ManagementSuite\Setup for Version value, or inspect the file core\config\version.xml if accessible
    Affected if Unable to retrieve version information
  3. Compare version against affected ranges
    Review the retrieved version number against the affected ranges: versions before 2022 SU6, or version 2024 before the September update. Versions 2022 SU6 and later, or 2024 September update and later, are not affected
    Affected if Installed version is 2022 before SU6, or is 2024 before the September update
  4. Verify admin access configuration
    Review user accounts with administrative privileges in EPM console under Administration > Users or Security > Administrators. Confirm if any non-intended admin accounts exist
    Affected if Unrecognized or unauthorized admin accounts are present in the system

The environment is affected if Ivanti Endpoint Manager is installed and the installed version falls before 2022 SU6 or is 2024 before the September update, combined with the presence of admin-level access that could be exploited.

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 or later
Fixed in 2022
Interim mitigation

Apply the vendor-supplied patch: upgrade to Ivanti EPM 2022 SU6 or later, or deploy the 2024 September update. Prior to deployment, verify the current version in the environment and test the update in a non-production environment.

Recommended fix High confidence

2022 SU6 (Service Update 6) or later for 2022.x versions; September 2024 update or later for 2024.x versions

  1. Identify the current Ivanti Endpoint Manager version running in your environment
  2. For 2022.x versions: Upgrade to 2022 SU6 (Service Update 6) or later
  3. For 2024.x versions: Upgrade to the September 2024 update or later
  4. For versions prior to 2022: Upgrade to at least 2022 SU6 as the minimum supported release
  5. Download the update from the Ivanti portal or official channels
  6. Apply the update following Ivanti's standard upgrade documentation for EPM
  7. Verify the version after update matches a fixed release
Caveat Security patch update; review Ivanti release notes for any compatibility or configuration changes

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

Fix this in Endpoint Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-32840 — 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-2024-32840 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