dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2024-50326

HIGH · 7.2 CVSS v3.1 Published 2024-11-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
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 execute arbitrary operating system commands via SQL injection, achieving remote code execution.

MitigationApply the November 2024 Security Update or the 2022 SU6 November Security Update (depending on the deployed version) to remediate this 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. Confirm Ivanti Endpoint Manager is installed
    Identify the installed product by checking the application name in Programs and Features (Windows) or using 'rpm -qa | grep -i ivanti' or 'dpkg -l | grep -i ivanti' (Linux)
    Affected if The product is not Ivanti Endpoint Manager
  2. Determine the installed version
    Check the version through the application UI (typically in Help > About) or check registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{GUID}\DisplayVersion, or query the Ivanti Core Server database version table
    Affected if The version matches < 2022, = 2022, or = 2024 (compare your installed version to these affected ranges)
  3. Verify admin interface accessibility
    Check if the Ivanti Endpoint Manager admin web console (typically port 443 or 8080) is exposed and accessible from the network
    Affected if The admin interface is reachable without additional authentication barriers
  4. Confirm admin privileges exist
    Review user accounts in the Ivanti Endpoint Manager console to identify accounts with Administrator or full admin rights
    Affected if There are active admin-level accounts that could be used to trigger the SQL injection

The environment is affected if Ivanti Endpoint Manager is installed with a version matching < 2022, = 2022, or = 2024 and an attacker could obtain admin credentials to access the management interface.

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 the 2022 SU6 November Security Update (depending on the deployed version) to remediate this vulnerability.

Recommended fix High confidence

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

  1. 1. Identify the current version of Ivanti Endpoint Manager installed
  2. 2. If running version 2022, plan upgrade to 2022 SU6 (November Security Update)
  3. 3. If running version 2024, plan upgrade to 2024 November Security Update
  4. 4. Review Ivanti upgrade documentation and release notes for the target version
  5. 5. Perform a full backup of the database and configuration
  6. 6. Schedule maintenance window for the upgrade
  7. 7. Apply the appropriate November Security Update (2024 or 2022 SU6)
  8. 8. Verify the upgrade completed successfully
Caveat Review Ivanti release notes for any breaking changes or behavior changes between current and patched versions; ensure compatibility with existing integrations

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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