dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2024-32845

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

SQL injection vulnerability in Ivanti Endpoint Manager (EPM) allows a remote authenticated attacker with admin privileges to execute arbitrary SQL queries, which can be leveraged to achieve remote code execution. The vulnerability affects versions before 2022 SU6 or the 2024 September update.

MitigationApply vendor-supplied patches (2022 SU6 or 2024 September update) immediately. Limit admin access to trusted personnel and monitor for indicators of compromise.

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 installation
    Check system for Ivanti Endpoint Manager components - look for the EPM server or console installation in Program Files, Program Files (x86), or the management server directory. On Windows, also check Add/Remove Programs or Get-WmiObject win32_product for installed packages named 'Ivanti Endpoint Manager' or 'LANDesk'.
    Affected if The product is not installed or this specific product is not present on the system.
  2. Identify installed EPM version
    Locate the EPM version information - common locations include: the core server console about dialog, the registry under HKLM\SOFTWARE\LANDesk\Manage\Settings\Core or HKLM\SOFTWARE\Ivanti\EndpointManager, or version.txt/version.ini files in the installation directory. Compare your found version against the affected ranges: versions before 2022 SU6, any 2022.x version, or any 2024 version before the September update.
    Affected if The installed version falls into any of these ranges: < 2022, 2022.x (any version before SU6), or 2024 (any version before the September 2024 update).
  3. Verify admin web console accessibility
    Check if the EPM administrative web interface (typically ports 80/443 or 8080/8443) is exposed to network access. Review firewall rules, IIS/Apache bindings, and network ACLs controlling access to the EPM console URLs such as /ldconsole, /landesk, or the main web portal.
    Affected if The admin web console is externally accessible beyond trusted admin workstations.
  4. Review admin account configuration
    Examine EPM console for admin users with privileges. Check local EPM user groups (typically 'Administrator' or 'Full Administrative' roles) or integrated directory accounts with EPM admin rights. Note that the vulnerability requires an attacker with admin-level privileges.
    Affected if There are admin accounts configured, particularly if they include integrated directory accounts or service accounts accessible to potential attackers.

Your environment is affected if Ivanti Endpoint Manager is installed and the version is any 2022.x version before SU6, or any 2024 version before the September update, with an accessible admin interface.

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 vendor-supplied patches (2022 SU6 or 2024 September update) immediately. Limit admin access to trusted personnel and monitor for indicators of compromise.

Recommended fix High confidence

Ivanti EPM 2022 SU6 or later; Ivanti EPM September 2024 update or later

  1. Upgrade Ivanti Endpoint Manager (EPM) 2022 to Service Update 6 (SU6) or later
  2. Upgrade Ivanti Endpoint Manager (EPM) 2024 to the September 2024 update or later
  3. After upgrading, verify the SQL injection vulnerability is no longer present by reviewing release notes and testing

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

Fix this in Endpoint Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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