dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2024-32848

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 · moderate confidence

SQL injection vulnerability in Ivanti Endpoint Manager (EPM) allows an authenticated attacker with admin privileges to execute arbitrary SQL queries, which can be leveraged to achieve remote code execution on the underlying system.

MitigationApply vendor patches: either version 2022 SU6 or later, or the September 2024 update. Ensure admin access controls are properly audited and monitor for unauthorized admin account activity.

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. Identify Ivanti Endpoint Manager installation
    Check for Ivanti Endpoint Manager (EPM) software on the system. Common installation paths may include C:\Program Files\Ivanti\ or check Windows Programs and Features for 'Ivanti Endpoint Manager' or 'LANDesk' (older naming).
    Affected if Ivanti Endpoint Manager is installed and version is 2022 or 2024, or any version prior to 2022 (not patched).
  2. Determine installed EPM version
    Open Windows Control Panel > Programs and Features, or check the registry under HKLM\SOFTWARE\LANDesk\Manage\Setup\, or run 'ldisu status' from the EPM command-line tools if available.
    Affected if Version matches < 2022, = 2022, or = 2024 (unpatched).
  3. Verify admin access controls
    Review admin accounts configured in EPM via the console under Administration > Users or Security > Administrators. Check for unauthorized or unexpected admin-level accounts.
    Affected if Any admin account exists in EPM (exploitation requires admin privileges).
  4. Audit recent admin activity logs
    Check EPM event logs or audit logs for suspicious SQL query execution, unusual admin login times, or unexpected configuration changes. Look for logs containing SQL syntax or database errors.
    Affected if Any anomalous admin activity or SQL errors found in logs.

If Ivanti Endpoint Manager version 2022 or 2024 (or any version prior to 2022) is installed and has admin accounts configured, the environment is potentially affected by this SQL injection vulnerability.

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 patches: either version 2022 SU6 or later, or the September 2024 update. Ensure admin access controls are properly audited and monitor for unauthorized admin account activity.

Recommended fix High confidence

Ivanti EPM 2022 SU6 (Service Update 6) or the 2024 September update (or later)

  1. 1. Identify the current version of Ivanti Endpoint Manager (EPM) by checking the server console or using the Administration > System Overview page
  2. 2. If running a version prior to 2022 SU6, plan an upgrade to Ivanti EPM 2022 SU6 (Service Update 6) or later
  3. 3. If running version 2024 (without the September update), plan an upgrade to the 2024 September update or later
  4. 4. Before upgrading, backup the database and create a snapshot/image of the EPM server for rollback capability
  5. 5. Download the appropriate update from Ivanti's support portal (requires valid maintenance contract)
  6. 6. Apply the upgrade during a scheduled maintenance window following Ivanti's official upgrade documentation
  7. 7. After upgrade, verify the SQL injection vulnerability is remediated by confirming the patch is applied
  8. 8. Test critical EPM functions (patch deployment, software distribution, inventory) to ensure normal operations
Caveat Review Ivanti release notes for breaking changes between current version and target upgrade version; test in non-production environment first

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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