dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2024-34780

HIGH · 7.2 CVSS v3.1 Published 2024-11-13
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
SQL injection in Ivanti Endpoint Manager before 2024 November Security Update or 2022 SU6 November Security 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 allows a remote authenticated attacker with admin privileges to achieve remote code execution. The vulnerability affects versions prior to the November 2024 security update or the 2022 SU6 November Security Update.

MitigationApply the November 2024 security update (or 2022 SU6 November Security Update for legacy versions) to Ivanti Endpoint Manager to address the SQL injection vulnerability.

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. Identify if Ivanti Endpoint Manager is installed
    Check installed programs or running services for 'Ivanti Endpoint Manager' or 'LanDesk' (the older product name)
    Affected if The software is present on the system
  2. Determine the installed version of Ivanti Endpoint Manager
    Access the admin console or check registry/source files for the version number (typically found in About section or installation directory)
    Affected if Version is 2022, 2024, or any version prior to the November 2024 security update
  3. Verify if the November 2024 security update or 2022 SU6 November Security Update has been applied
    Check the patch/update history within the Ivanti Endpoint Manager admin interface or system update logs
    Affected if Neither the November 2024 update nor the 2022 SU6 November Security Update appears in the applied patches
  4. Confirm admin interface accessibility
    Check if the Ivanti Endpoint Manager web console (typically port 8080 or 443) is exposed to network access
    Affected if The admin console is reachable from untrusted networks without proper network segmentation
  5. Review admin account activity logs
    Examine Ivanti Endpoint Manager logs for any suspicious SQL queries or admin actions from unexpected sources
    Affected if There are signs of SQL injection attempts or unauthorized admin sessions

A user is affected if Ivanti Endpoint Manager is installed and the version is 2022, 2024, or prior to November 2024 without the November 2024 or 2022 SU6 November Security Update applied.

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 November 2024 security update (or 2022 SU6 November Security Update for legacy versions) to Ivanti Endpoint Manager to address the SQL injection vulnerability.

Recommended fix High confidence

2024 November Security Update or 2022 SU6 November Security Update

  1. 1. Identify the current version of Ivanti Endpoint Manager by checking the product console or system information
  2. 2. Review Ivanti Endpoint Manager version compatibility to determine whether to upgrade to 2024 November Security Update or 2022 SU6 November Security Update
  3. 3. Create a full backup of the Ivanti Endpoint Manager database and configuration
  4. 4. Download the appropriate November Security Update from Ivanti's official support portal (forks.ivanti.com)
  5. 5. Apply the security update following Ivanti's official patch installation documentation
  6. 6. Verify the update was applied successfully by checking the product version
  7. 7. Validate that the SQL injection vulnerability is no longer present

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
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
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,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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