dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2024-32841

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

MitigationApply the November Security Update for either Ivanti Endpoint Manager 2024 or 2022 SU6, depending on the currently deployed 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
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 the installed Ivanti Endpoint Manager version
    Check the product version through the Admin UI under 'Help > About' or locate the version file in the installation directory (typically in the core server folder). Alternatively, query the registry key: HKLM\SOFTWARE\LANDesk\LDMain\CurrentVersion on the core server.
    Affected if The displayed version is 2022 (any Service Pack/Update) or 2024 (any Update), or any version numerically lower than 2022.
  2. Confirm admin account access exists
    Log into the Ivanti Endpoint Manager admin console (LANDESK Management Suite console) using admin credentials. Navigate to 'Security > User' or 'Administration > Users' to enumerate admin-level accounts configured in the system.
    Affected if At least one user account with Administrator privileges is present and enabled in the console.
  3. Verify the core server web component is enabled
    The vulnerability exploits the web-based admin interface. Confirm the 'LDMS Web Console' or 'Ivanti Endpoint Manager Web Console' service is running on the core server. Check via Windows Services (services.msc) for 'LDMS Web Console' or by attempting to access the web portal at https://[server]/landesk on the network.
    Affected if The web console service is installed and running, making the SQL injection attack surface accessible over HTTP/HTTPS.

You are affected if your Ivanti Endpoint Manager version is 2022, 2024, or any version below 2022 AND the admin web interface is accessible with at least one admin account configured.

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 either Ivanti Endpoint Manager 2024 or 2022 SU6, depending on the currently deployed version.

Recommended fix High confidence

2024 November Security Update or 2022 SU6 November Security Update

  1. Back up the Ivanti Endpoint Manager database and configuration before starting the upgrade
  2. Determine current version by checking About or version information in the console
  3. For version 2024: Download and install the 2024 November Security Update from Ivanti support portals
  4. For version 2022: Download and install the 2022 SU6 November Security Update from Ivanti support portals
  5. Follow Ivanti's standard upgrade documentation for your specific version
  6. Verify the upgrade was successful by checking the version number post-installation
  7. Confirm the SQL injection vulnerability is resolved by verifying the patch is applied

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-32841 — 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-32841 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