dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2024-29828

HIGH · 8.0 CVSS v3.1 Published 2024-05-31
Fix available
A fix is available. Upgrade to 2022 or later.
See remediation →
82/100
Remediation priority · High
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 authenticated 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 of Ivanti Endpoint Manager (EPM) 2022 SU5 and prior allows an authenticated attacker on the same network to inject malicious SQL queries that can lead to remote code execution on the affected system.

MitigationApply Ivanti's vendor patch for this vulnerability immediately. Until patched, restrict network access to the Core server to trusted IP addresses and ensure database service accounts follow least-privilege principles.

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

CVSS:3.1/AV:A/AC:L/PR:L/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
    Locate the Ivanti Endpoint Manager installation on the system and determine its version number. This is typically accessible through the product's About or Help section in the management console, or via installed program information in Windows Add/Remove Programs.
    Affected if The installed version is 2022 or any version prior to 2022 Service Update 5 (SU5)
  2. Determine the exact version and build number
    Retrieve the full version and build number of the installed Ivanti Endpoint Manager. Compare this against the 2022 SU5 release to confirm whether the installed version includes the patch or falls within the affected range.
    Affected if The version is 2022 with any service update prior to SU5, or the exact version cannot be confirmed as post-SU5
  3. Verify Core server component status
    Confirm that the Ivanti Endpoint Manager Core server component is installed and running on the affected system. This is the component where the SQL injection vulnerability exists.
    Affected if The Core server component is present and operational on the system
  4. Assess network accessibility of the Core server
    Determine if the Core server is accessible over the network. The vulnerability requires an authenticated attacker on the same network to exploit the SQL injection. Check network binding configurations and firewall rules.
    Affected if The Core server is reachable over the network from systems other than localhost

The environment is affected if Ivanti Endpoint Manager version 2022 or prior (pre-SU5) is installed with the Core server component exposed to network access.

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 Ivanti's vendor patch for this vulnerability immediately. Until patched, restrict network access to the Core server to trusted IP addresses and ensure database service accounts follow least-privilege principles.

Recommended fix Moderate confidence

Ivanti Endpoint Manager 2022 SU6 or later / Endpoint Manager 2023 and above

  1. 1. Identify current Ivanti Endpoint Manager version by checking the Core server's 'About' or version information panel
  2. 2. Navigate to the Ivanti Customer Portal (portal.ivanti.com) and access the Downloads section
  3. 3. Locate the latest available version of Endpoint Manager 2022 (Service Update 6 or later) or the newest major version
  4. 4. Download the installer package for the fixed version
  5. 5. Review the provided Release Notes and Upgrade Guide for pre-installation requirements
  6. 6. Execute a full backup of the Endpoint Manager database and Core server configuration
  7. 7. Apply the upgrade following the official Installation/Upgrade documentation
  8. 8. Verify the upgrade by logging into the Core server and confirming the new version number
Caveat Review release notes for potential configuration changes; ensure compatibility with existing agents and third-party integrations before upgrading

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
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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