dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2024-29830

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 in the Core server component of Ivanti Endpoint Manager (EPM) 2022 SU5 and prior allows an authenticated attacker to execute arbitrary code, likely through database command execution capabilities such as xp_cmdshell. The attacker requires network proximity to the affected system.

MitigationApply vendor patch for CVE-2024-29830; until patch is available, restrict network access to Core server and monitor for suspicious SQL patterns in logs. Upgrade to a supported version if current is end-of-life.

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 software on the target system and confirm it is the Core server component. Check installed programs or service listings for 'Ivanti Endpoint Manager' or 'EPM'.
    Affected if The software is present and is the Core server component.
  2. Determine installed version
    Check the installed version of Ivanti Endpoint Manager. Compare against the affected versions: any 2022 version (including all SU updates up to and including SU5) and any prior major version.
    Affected if The installed version is 2022 with any update level, or any version prior to 2022.
  3. Verify Core server network accessibility
    Determine if the Core server is exposed to the network. Check firewall rules, listening ports (typically port 443 or configured EPM ports), and network ACLs that allow external access to the Core server.
    Affected if The Core server is accessible from network segments beyond the trusted internal network, increasing exposure risk.
  4. Confirm SQL database configuration
    Inspect whether the Microsoft SQL Server database used by EPM has advanced stored procedures enabled, particularly xp_cmdshell or similar command execution features. Check SQL Server configuration settings.
    Affected if xp_cmdshell or equivalent database command execution features are enabled on the EPM database server.
  5. Review authentication exposure
    Assess whether the EPM console is accessible with valid credentials from the network. Check for default credentials, weak password policies, or exposed administrative interfaces.
    Affected if The Core server accepts authentication from untrusted network sources, allowing an authenticated attacker to exploit the SQL injection.

A user is affected if they have Ivanti Endpoint Manager 2022 (any SU) or prior running a Core server that is network-accessible with SQL injection present in the Core component.

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 patch for CVE-2024-29830; until patch is available, restrict network access to Core server and monitor for suspicious SQL patterns in logs. Upgrade to a supported version if current is end-of-life.

Recommended fix Moderate confidence

Ivanti Endpoint Manager 2022 SU6 or later (2022 Service Update after SU5)

  1. Download the latest Ivanti Endpoint Manager 2022 Service Update (SU6 or later) from the official Ivanti download portal
  2. Review the release notes for any prerequisites or additional patches required
  3. Back up the Ivanti EPM database and configuration files
  4. Stop all Ivanti services on the Core server
  5. Install the new Service Update on the Core server following the official installation guide
  6. Verify all services start successfully after the update
  7. Confirm the SQL Injection vulnerability is resolved by reviewing the patch notes
  8. Test critical EPM functions (agent deployment, software distribution, patching) to ensure normal operation
Caveat Review release notes for any deprecated features or configuration changes required; test in non-production first

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

Fix this in Endpoint Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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