dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2024-29826

HIGH · 8.8 CVSS v3.1 Published 2024-05-31
Fix available
A fix is available. Upgrade to 2022 or later.
See remediation →
93/100
Remediation priority · Urgent
High EPSS No privileges 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 vulnerability in Core server of Ivanti EPM 2022 SU5 and prior allows an unauthenticated attacker within the same network to execute arbitrary code.

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 the Core server component of Ivanti Endpoint Manager (EPM) 2022 SU5 and prior allows an unauthenticated attacker with network access to execute arbitrary code through specially crafted SQL queries.

MitigationUpgrade to Ivanti EPM 2022 SU6 or later to patch the vulnerability; apply network segmentation to restrict access to the Core server to only trusted systems.

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

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

CVSS:3.1/AV:A/AC:L/PR:N/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 if Ivanti Endpoint Manager is installed
    Locate the Ivanti Endpoint Manager installation directory, typically under C:\Program Files\Ivanti\ or check Windows Programs and Features for 'Ivanti Endpoint Manager'
    Affected if Ivanti Endpoint Manager is not found on the system, this CVE does not apply
  2. Determine the installed EPM version
    Open the Ivanti Endpoint Manager console, go to Help > About, or check the version information in the installation directory or Windows registry under HKLM\SOFTWARE\Ivanti\EndpointManager
    Affected if The version is 2022 SU5 or earlier, or any version numbered 2022 (including SU1-SU5), or any version below 2022
  3. Confirm the Core server component is present
    Verify the Core server component is installed - check for the 'Core' service or server component in the Ivanti EPM installation, typically found in the main installation folder under 'Core' or 'Server' subdirectories
    Affected if The Core server component is not present, the SQL injection vector may not be accessible
  4. Check network exposure of the Core server
    Review firewall rules and network configuration to determine if the Core server port (typically port 443 or as configured) is exposed to untrusted networks
    Affected if The Core server is directly accessible from untrusted networks without proper segmentation, an unauthenticated attacker could reach the vulnerable SQL injection endpoint

If the installed Ivanti Endpoint Manager version is 2022 SU5 or prior (including any 2022 edition before SU6), the system is affected by this vulnerability and the Core server should not be network-exposable to untrusted hosts.

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

Upgrade to Ivanti EPM 2022 SU6 or later to patch the vulnerability; apply network segmentation to restrict access to the Core server to only trusted systems.

Recommended fix Moderate confidence

Upgrade to Ivanti Endpoint Manager 2022 SU6 or later (2023/2024 recommended)

  1. 1. Identify the current Ivanti Endpoint Manager version installed (e.g., check About or version info in the admin console)
  2. 2. If running version 2022 SU5 or prior, plan for an upgrade to a newer version
  3. 3. Download the updated Ivanti EPM installer from the official Ivanti portal or authorized distribution channel
  4. 4. Before upgrading, perform a complete backup of the database and configuration
  5. 5. Test the upgrade in a non-production environment first
  6. 6. Apply the upgrade during a planned maintenance window
  7. 7. Verify the upgrade was successful and the version is newer than 2022 SU5
  8. 8. Confirm the SQL injection vulnerability is no longer present
Caveat Review Ivanti release notes for any configuration or feature changes between versions; test third-party integrations

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 / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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