dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2024-50323

HIGH · 7.8 CVSS v3.1 Published 2024-11-12
Fix available
A fix is available. Upgrade to 2022 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 local unauthenticated attacker to achieve code execution. User interaction is required.

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 local unauthenticated attacker to execute code by injecting malicious SQL queries. The attack requires user interaction to trigger, but achieves full code execution on the affected system.

MitigationApply the November Security Update for Ivanti Endpoint Manager (2024) or the 2022 SU6 November Security Update, depending on the installed version.

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 the list of installed applications on the system for 'Ivanti Endpoint Manager' or legacy 'LANDesk Management' entries
    Affected if The application is not found in the installed programs list, then the system is not affected
  2. Determine the installed version of Ivanti Endpoint Manager
    Open the Ivanti Endpoint Manager console and navigate to Help > About, or check the Windows Programs and Features list for the version number displayed
    Affected if The displayed version matches < 2022 (any version before 2022), equals 2022, or equals 2024
  3. Confirm the exact version number against affected ranges
    Compare the installed version number to the affected ranges: versions before 2022, version 2022, and version 2024
    Affected if The version falls into any of these categories: any 2021.x or earlier, specifically version 2022 (any patch level), or specifically version 2024 (any patch level)
  4. Verify the SQL injection attack surface exists
    Determine if the web components or remote reporting features of Ivanti Endpoint Manager are accessible and enabled, as the SQL injection occurs through these interfaces
    Affected if The web console or reporting services are accessible without additional authentication barriers beyond what the product normally requires

A system is affected if Ivanti Endpoint Manager is installed and the installed version is before 2022, is exactly version 2022, or is exactly version 2024.

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 Security Update for Ivanti Endpoint Manager (2024) or the 2022 SU6 November Security Update, depending on the installed version.

Recommended fix High confidence

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

  1. Verify current Ivanti Endpoint Manager version by checking the console or using the administration tools
  2. Download the appropriate November Security Update from the Ivanti Customer Portal (https://forums.ivanti.com or official Ivanti download channels)
  3. For Endpoint Manager 2024 users: Apply the 2024 November Security Update
  4. For Endpoint Manager 2022 users: Apply the 2022 SU6 November Security Update
  5. After upgrade, verify the SQL injection vulnerability is remediated by confirming the patch is installed
  6. Review release notes for any additional configuration changes required post-update

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
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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