dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2024-34779

HIGH · 7.2 CVSS v3.1 Published 2024-09-12
Fix available
A fix is available. Upgrade to 2022 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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 in Ivanti EPM before 2022 SU6, or the 2024 September update allows a remote authenticated attacker with admin privileges to achieve remote code execution.

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 Ivanti Endpoint Manager (EPM) allows a remote authenticated attacker with admin privileges to execute arbitrary code. The vulnerability affects versions prior to 2022 SU6 or the 2024 September update.

MitigationApply the vendor-supplied patch by upgrading to 2022 SU6 or later, or deploying the 2024 September update. Additionally, review and restrict admin-level access accounts to minimize 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= 2024

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

CVSS:3.1/AV:N/AC:L/PR:H/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. Confirm Ivanti Endpoint Manager is installed
    Check for the Ivanti Endpoint Manager service or look for related processes in Task Manager. Common installation paths: C:\Program Files\Ivanti\ or C:\Program Files\LANDesk\
    Affected if The product is not Ivanti Endpoint Manager
  2. Identify installed EPM version
    Open the EPM console, go to Help > About, or check the registry key: HKEY_LOCAL_MACHINE\SOFTWARE\LANDesk\ManagementSuite\Setup\ProductVersion
    Affected if Version cannot be determined or is not visible
  3. Compare version to affected ranges
    If version shows 2022.x, check if SU6 is applied (look for SU6 in patch notes or version string). For 2024.x, verify if the September update is installed
    Affected if Version is 2022 (any build) OR version is 2024 prior to September update OR version is earlier than 2022
  4. Verify admin interface accessibility
    Check if the EPM admin web console (typically ports 8080, 8443, or 443) is exposed to network. Review firewall rules and IIS bindings
    Affected if Admin console is externally accessible without restriction

Environment is affected if Ivanti Endpoint Manager is installed with version 2022 (any build), 2024 (before September update), or any version prior to 2022, and the admin interface is network-accessible.

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 by upgrading to 2022 SU6 or later, or deploying the 2024 September update. Additionally, review and restrict admin-level access accounts to minimize attack surface.

Recommended fix High confidence

2022 SU6 (Security Update 6) or 2024 September update

  1. Check current Ivanti Endpoint Manager version in the system console or about section
  2. If running version 2022 or any version before 2022 SU6: Plan upgrade to Ivanti EPM 2022 SU6 (Security Update 6)
  3. If running version 2024 prior to September: Plan upgrade to the 2024 September update
  4. Before upgrading, create a complete backup of the database and configuration
  5. Apply the upgrade following Ivanti's standard upgrade procedures
  6. After upgrade, verify the version matches the fixed release in the console
  7. Confirm core Endpoint Manager functionality operates normally post-upgrade
Caveat Review Ivanti upgrade documentation for version-specific migration requirements; ensure adequate testing environment validation before production deployment

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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
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,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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