dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2024-29846

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 · high confidence

SQL injection vulnerability in the Core server component of Ivanti Endpoint Manager (EPM) 2022 SU5 and prior versions allows an authenticated attacker with network access to inject malicious SQL queries, potentially leading to arbitrary code execution on the affected system.

MitigationApply vendor-supplied patches for Ivanti EPM 2022 SU5 and prior. If patches are unavailable, restrict network access to the Core server to trusted internal networks only and review application logs for suspicious SQL activity.

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 installed Ivanti EPM version
    Locate the EPM version through the console or registry (typically found in Add/Remove Programs, or via the Core server console under About/System Information). Compare the version number to the affected range: 2022 SU5 and prior, or any version marked as 2022 or lower.
    Affected if The installed version is 2022 SU5 or earlier, or is listed as version 2022 or any sub-version (e.g., 2022 SU1, SU2, etc.).
  2. Confirm Core server component is present and running
    Verify the Ivanti Endpoint Manager Core service is installed and active on the system. This is typically visible in Windows Services (galaxycore service) or via the EPM administration console.
    Affected if The Core server component is installed and running on the target system.
  3. Check network exposure of the Core server
    Review network listener configurations and firewall rules to determine if the Core server (typically port 443 or as configured during installation) is accessible from outside trusted internal networks.
    Affected if The Core server port is open to untrusted networks or the internet.
  4. Review application logs for suspicious SQL patterns
    Examine EPM Core server logs (located in the EPM installation directory under Logs or in Windows Event Viewer under Application logs) for unusual SQL syntax, unexpected database queries, or patterns indicative of injection attempts.
    Affected if Logs contain malformed SQL statements, unexpected database queries from low-privilege accounts, or error messages referencing SQL syntax violations.
  5. Check for unauthorized code execution indicators
    Review the file system for unexpected executables in the EPM directory, new scheduled tasks created by the service account, or unauthorized changes to database stored procedures.
    Affected if New or modified executable files exist in the EPM directories, or unauthorized scheduled tasks/scripts are present.

The environment is affected if the installed Ivanti EPM version is 2022 SU5 or prior (including any 2022.x version), the Core server is present, and it is accessible over the network to authenticated users.

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-supplied patches for Ivanti EPM 2022 SU5 and prior. If patches are unavailable, restrict network access to the Core server to trusted internal networks only and review application logs for suspicious SQL activity.

Recommended fix Moderate confidence

Ivanti Endpoint Manager 2022 SU6 or later (2022.1 or newer stable release)

  1. 1. Identify current Ivanti Endpoint Manager version by checking the Core server console or registry
  2. 2. Navigate to the Ivanti Customer Portal (https://login.ivanti.com/) or download center
  3. 3. Download Ivanti Endpoint Manager 2022 Service Update 6 (SU6) or later
  4. 4. Back up the Ivanti EPM database and Core server configuration
  5. 5. Apply the update during a maintenance window following Ivanti's official upgrade documentation
  6. 6. Verify the Core server services restart successfully
  7. 7. Confirm the SQL injection vulnerability is remediated by checking the patch version
Caveat Review Ivanti EPM 2022 SU6 release notes for any configuration or feature changes before upgrading; ensure compatibility with existing agents and 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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
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,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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