dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2024-50328

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 an authenticated attacker with admin privileges to inject malicious SQL queries, which can be leveraged to achieve remote code execution on the underlying system.

MitigationApply the November 2024 Security Update for Ivanti Endpoint Manager 2024, or the 2022 SU6 November Security Update for legacy versions. Restrict admin access to trusted personnel and monitor for anomalous database queries.

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 Ivanti Endpoint Manager installation
    Locate Ivanti Endpoint Manager installation directory (typically C:\Program Files\LANDesk\ or C:\Program Files\Ivanti\), or check Windows Services for 'LANDesk Management Server' or 'Ivanti Endpoint Manager' service
    Affected if The product is installed on the system
  2. Determine installed version
    Check the version of Ivanti Endpoint Manager by inspecting the About page in the admin console, or check the version info of the core service executable (LDMain.exe or similar in the installation directory)
    Affected if Installed version is 2022 or 2024, or any version prior to 2022 (all fall within the < 2022, = 2022, or = 2024 affected ranges)
  3. Verify admin web console accessibility
    Confirm the Ivanti Endpoint Manager admin console (typically on port 80/443 or 8080/8443) is reachable and requires authentication
    Affected if The admin interface is exposed and accessible (required condition for authenticated attacker to exploit)
  4. Confirm admin privileges requirement
    Review that exploitation requires an authenticated session with admin-level privileges to the Endpoint Manager console
    Affected if Any admin-level user account exists in the system (the vulnerability requires admin authentication to inject SQL)

The environment is affected if Ivanti Endpoint Manager version 2022 or 2024 (or any version prior to 2022) is running and the admin interface is accessible with admin-level accounts.

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 for Ivanti Endpoint Manager 2024, or the 2022 SU6 November Security Update for legacy versions. Restrict admin access to trusted personnel and monitor for anomalous database queries.

Recommended fix Moderate confidence

2024 November Security Update or 2022 SU6 November Security Update (depending on your base version)

  1. Verify current Ivanti Endpoint Manager version by navigating to https://<server>/node/wip and checking the build number
  2. Download the November 2024 Security Update or the 2022 SU6 November Security Update from the Ivanti Customer Portal (requires valid support account)
  3. Create a full backup of the Endpoint Manager database and virtual machine/snapshot before proceeding
  4. Test the update in a non-production environment first to verify compatibility with existing integrations
  5. Apply the security update during a planned maintenance window following Ivanti's standard upgrade documentation
  6. After upgrade, verify the SQL injection vulnerability is remediated by confirming the patch version is applied
  7. Review and validate that core Endpoint Manager functionality (patch deployment, software distribution, inventory) works post-update
Caveat Standard upgrade risks apply - test thoroughly in staging before production deployment; verify third-party integrations and custom scripts are compatible with the new version

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
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
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,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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