dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2024-29825

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

An unauthenticated SQL Injection vulnerability exists in the Core server component of Ivanti Endpoint Policy Manager (EPM) 2022 SU5 and prior versions. An attacker on the same network can inject malicious SQL queries to execute arbitrary code on the affected system without requiring authentication.

MitigationApply the vendor-supplied patch for Ivanti EPM 2022 SU5 and prior. If patching is immediately infeasible, restrict network access to the Core server to trusted personnel only using network segmentation and firewall rules to reduce the attack surface.

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. Verify Ivanti Endpoint Policy Manager is installed
    Check the Windows installed programs list or look for the Ivanti EPM service in Services.msc
    Affected if The product is present on the system
  2. Determine the installed version
    Check the program version through Add/Remove Programs, or look in the installation directory for version information files
    Affected if The version is 2022 or any version prior to 2022 SU5 (such as 2022 SU4, SU3, etc.)
  3. Confirm the Core server component is running
    Look for the Core service process in Windows Task Manager or check Services for the Ivanti Endpoint Manager Core service
    Affected if The Core server service is running and enabled
  4. Verify network accessibility of the Core server
    Check firewall rules and network configuration to determine if the Core server port (typically port 8080 or as configured) is exposed to the network
    Affected if The Core server is reachable from the network without authentication restrictions

You are affected if Ivanti Endpoint Policy Manager 2022 or any prior version is installed with the Core server component exposed to the network.

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 the vendor-supplied patch for Ivanti EPM 2022 SU5 and prior. If patching is immediately infeasible, restrict network access to the Core server to trusted personnel only using network segmentation and firewall rules to reduce the attack surface.

Recommended fix Moderate confidence

Ivanti EPM 2022 SU6 or later (contact Ivanti for exact fixed version)

  1. Check current Ivanti Endpoint Manager version by navigating to Help > About in the EPM console
  2. Identify if version is 2022 SU5 or prior (e.g., 2022, 2022 SU1, 2022 SU2, 2022 SU3, 2022 SU4)
  3. Contact Ivanti Customer Support or check forums.ivanti.com for the specific patched version/release that addresses CVE-2024-29825
  4. Download the patched version from the Ivanti portal or obtain the SU6 (or later) update
  5. Before applying in production, test the upgrade in a non-production environment
  6. Schedule maintenance window and apply the upgrade following Ivanti's standard upgrade documentation
  7. Verify the upgrade was successful and the vulnerability is addressed
  8. Monitor Ivanti forums and security advisories for any post-patch requirements
Caveat Review release notes for potential configuration or compatibility changes between SU5 and the patched version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Endpoint Manager Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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