dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2024-34781

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
High EPSS 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 an authenticated attacker with admin privileges to execute arbitrary SQL queries, which can be chained 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 appropriate November Security Update for either the 2024 or 2022 (SU6) release train depending on your current version branch.

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. Locate installed Ivanti Endpoint Manager version
    Access the Ivanti Endpoint Manager admin console and navigate to the About or System Information page to view the installed software version
    Affected if Version displays as 2022 or 2024 (any build) or any version prior to the November 2024 security update
  2. Confirm version release train
    Note whether the installation is on the 2022 or 2024 release branch by checking the version identifier in the admin interface or application metadata
    Affected if Running the 2022 or 2024 release train without the November 2024 security update applied
  3. Identify admin privilege accounts
    Review the user management section of the Ivanti Endpoint Manager admin console to enumerate accounts with administrative-level permissions
    Affected if Any admin privileged user accounts exist in the system (the vulnerability requires admin-level access)
  4. Verify update installation status
    Check if the November 2024 security update or the 2022 SU6 November security update has been applied by reviewing the installed patches or update history in the system
    Affected if The November security updates have not been installed on the current version

The environment is affected if running Ivanti Endpoint Manager version 2022 or 2024 (or any version prior to November 2024) with admin user accounts present and without the November security updates 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 appropriate November Security Update for either the 2024 or 2022 (SU6) release train depending on your current version branch.

Recommended fix Moderate confidence

2022 SU6 November Security Update (for 2022.x) or 2024 November Security Update (for 2024.x)

  1. 1. Identify the current version of Ivanti Endpoint Manager by accessing the admin console and navigating to the About or System Information section
  2. 2. If running version 2022.x, plan to upgrade to '2022 SU6 November Security Update' or later
  3. 3. If running version 2024.x, plan to upgrade to '2024 November Security Update' or later
  4. 4. Review Ivanti's official upgrade documentation and release notes for the target security update
  5. 5. Create a full backup of the Endpoint Manager database and configuration before proceeding
  6. 6. Test the upgrade in a non-production environment first
  7. 7. Apply the November Security Update during a planned maintenance window
  8. 8. After upgrade, verify the version by checking the admin console and confirm the SQL injection vulnerability is remediated
Caveat Standard upgrade risks apply - test in staging environment 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
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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