dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2024-32847

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 affecting versions before the November 2024 security update (or 2022 SU6 November Security Update for older branches). A remote authenticated attacker with admin privileges can inject malicious SQL queries, which can be leveraged to achieve remote code execution.

MitigationApply the November 2024 security update for current versions, or the 2022 SU6 November Security Update for legacy 2022 installations. Prioritize patching given the high CVSS score and RCE capability.

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 version
    Locate the installed version through the product console, about page, or installation files. Common methods include checking the application GUI under Help > About, examining installation directory metadata, or querying the service information.
    Affected if Running version 2022 or 2024 (unpatched) or any version before 2022
  2. Confirm November 2024 security update status
    Check whether the November 2024 security update (or 2022 SU6 November Security Update for legacy installations) has been applied. This may be visible in the product console update history, installed patches list, or system information panel.
    Affected if The November 2024 security update has not been installed
  3. Verify admin privilege configuration
    Review the Ivanti Endpoint Manager admin user accounts and role assignments through the administration console. Identify accounts with administrator-level privileges.
    Affected if Administrative accounts exist in the system (this is the baseline condition for exploitation)

A system is affected if it runs Ivanti Endpoint Manager version 2022 or 2024 without the November 2024 security patch (or any version below 2022), regardless of admin account configuration since the vulnerability requires admin-level access to exploit.

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 current versions, or the 2022 SU6 November Security Update for legacy 2022 installations. Prioritize patching given the high CVSS score and RCE capability.

Recommended fix High confidence

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

  1. 1. Back up your Ivanti Endpoint Manager database and configuration before applying any update
  2. 2. Identify your current Endpoint Manager version (2022 or 2024 branch)
  3. 3. For 2024 branch users: Download and install the November Security Update for Endpoint Manager 2024
  4. 4. For 2022 branch users: Download and install SU6 November Security Update for Endpoint Manager 2022
  5. 5. Verify the update was applied successfully by checking the version in the admin console
  6. 6. Test critical functionality to ensure the update did not break existing workflows
  7. 7. Validate that the SQL injection vulnerability is remediated by reviewing system logs
Caveat Standard security update with no expected breaking changes; follow normal pre-update backup procedures

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
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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