dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2024-32842

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

Ivanti Endpoint Manager (EPM) contains an unspecified SQL injection vulnerability that allows a remote authenticated attacker with admin privileges to execute arbitrary code by injecting malicious SQL queries that lead to operating system command execution.

MitigationApply vendor-provided patches (2022 SU6 or the September 2024 update) to all affected Ivanti EPM installations. Since admin privileges are required for exploitation, review and minimize administrative access accounts as an additional defense-in-depth measure.

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
    Check system for Ivanti Endpoint Manager application - typically found in Program Files or via installed programs list (Add/Remove Programs on Windows)
    Affected if The software is present on the system
  2. Identify installed Ivanti EPM version
    Access the Ivanti EPM administration console or check version information through the application's About/Properties dialog, or query the installed software registry keys
    Affected if The detected version is < 2022, = 2022, or = 2024 (exact version numbers like 2022.1, 2022.2, etc. should be compared against these ranges)
  3. Verify admin accounts exist in the system
    Check Ivanti EPM user management console for accounts with administrator-level privileges
    Affected if Any admin-level accounts are configured and accessible (exploitation requires admin privileges)
  4. Review admin access controls
    Audit the list of users granted administrator rights within Ivanti EPM user management
    Affected if Multiple or weakly-controlled admin accounts exist, increasing exploitation risk
  5. Check for suspicious SQL activity
    Review Ivanti EPM server logs and database audit trails for unusual SQL query patterns that may indicate injection attempts
    Affected if Unexpected SQL syntax or command-like strings appear in logs

A user is affected if Ivanti Endpoint Manager is installed with a version matching < 2022, = 2022, or = 2024 AND at least one admin-privileged account exists in the system.

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-provided patches (2022 SU6 or the September 2024 update) to all affected Ivanti EPM installations. Since admin privileges are required for exploitation, review and minimize administrative access accounts as an additional defense-in-depth measure.

Recommended fix High confidence

2022 SU6 (Service Update 6) or 2024 September update

  1. Verify current Ivanti Endpoint Manager version in the admin console or via the About section
  2. Back up the Ivanti EPM database and configuration settings
  3. Download the appropriate fixed version from the Ivanti portal: either 2022 SU6 (Service Update 6) or the September 2024 release
  4. Follow Ivanti's standard upgrade documentation for your current version path
  5. Run the upgrade installer with administrative privileges
  6. Verify the upgrade completed successfully by checking the version number
  7. Confirm SQL injection vulnerability is patched by reviewing release notes or contacting Ivanti support

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-32842 — 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-32842 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