dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2024-32843

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 EPM allows a remote authenticated attacker with admin privileges to execute arbitrary code. The flaw exists in versions prior to 2022 SU6 or the 2024 September update.

MitigationApply vendor patches by updating Ivanti EPM to version 2022 SU6 or later, or to the 2024 September update.

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 EPM installation
    Locate the Ivanti Endpoint Manager installation in your environment - check for the core server component typically installed on Windows Server
    Affected if Ivanti Endpoint Manager is not installed, this CVE does not apply
  2. Determine the installed version
    Check the product version through Windows Programs and Features, or the application's About/Information dialog if accessible, or query the registry for the installed version string
    Affected if The version cannot be determined or is not clearly displayed
  3. Compare against vulnerable version ranges
    Review the installed version number against the affected ranges: versions < 2022, 2022 versions prior to SU6, or 2024 versions prior to the September update
    Affected if The installed version falls within any of these vulnerable ranges
  4. Confirm admin access context
    Determine if the Ivanti EPM installation has admin user accounts configured - the vulnerability requires an authenticated admin session to exploit
    Affected if No admin users exist or the application is not accessible to authenticated users, exploitation is not possible

You are affected if Ivanti Endpoint Manager is installed and the version is either prior to 2022 SU6, or is a 2024 version released before the September update.

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 by updating Ivanti EPM to version 2022 SU6 or later, or to the 2024 September update.

Recommended fix Moderate confidence

2022 SU6 or later, or 2024 September update or later (depending on the major version branch)

  1. 1. Identify the current installed version of Ivanti Endpoint Manager (EPM)
  2. 2. If running version 2022 (any patch level), upgrade to version 2022 SU6 or later
  3. 3. If running version 2024 (any patch level before September), upgrade to the September 2024 update or later
  4. 4. If running versions older than 2022, upgrade to a supported stable release such as 2022 SU6+ or the latest 2024 release
  5. 5. After upgrading, verify the SQL injection vulnerability is resolved by reviewing release notes for the target version
  6. 6. Test that normal EPM administrative functions work correctly post-upgrade
Caveat Upgrading major versions of Ivanti EPM may require testing of existing policies and configurations; review upgrade documentation for any required pre-upgrade steps

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
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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