dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2024-37376

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 a remote 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 2024 Security Update for Ivanti Endpoint Manager (2024 version) or the November 2024 Security Update for version 2022 SU6. Restrict admin access to trusted personnel and monitor for unusual SQL query patterns.

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 of Ivanti Endpoint Manager in the product UI under Help > About, or check the installer/log files. Compare the version number to the affected ranges: versions < 2022, version 2022, and version 2024.
    Affected if The installed version is 2022, 2024, or any version below 2022 (e.g., 2021, 2020). Versions 2023 and 2025+ are not listed as affected.
  2. Confirm admin access is available
    Verify whether the Ivanti Endpoint Manager admin console is accessible and check if admin user accounts are configured. Review user roles and permissions settings in the administration section.
    Affected if Admin-level accounts exist and can log into the Ivanti Endpoint Manager console. The vulnerability requires an authenticated attacker with admin privileges.
  3. Review SQL query logs for anomalies
    Examine Ivanti Endpoint Manager logs (typically found in the installation directory under Logs or in Windows Event Viewer) for unusual or unexpected SQL queries, especially those containing UNION, SELECT, or DROP statements that could indicate exploitation attempts.
    Affected if Unusual SQL queries appear in logs, particularly those containing SQL injection patterns or queries originating from admin sessions that are malformed or unexpected.
  4. Check for recent admin session anomalies
    Review admin login history and session logs for unexpected IP addresses, geographic locations, or times that do not match legitimate admin activity patterns.
    Affected if Admin sessions show logins from unknown sources, unusual geographic locations, or times that do not align with known administrator activity.

You are affected if your Ivanti Endpoint Manager version is 2022, 2024, or any version below 2022 AND an authenticated admin user account exists that could be leveraged by an attacker.

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 version) or the November 2024 Security Update for version 2022 SU6. Restrict admin access to trusted personnel and monitor for unusual SQL query patterns.

Recommended fix High confidence

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

  1. Identify current Ivanti Endpoint Manager version by checking the console or system information
  2. Review release notes for 2024 November Security Update or 2022 SU6 November Security Update for compatibility requirements
  3. Backup the current Endpoint Manager database and configuration
  4. Download the appropriate November Security Update from Ivanti support portal (2024 version or 2022 SU6 depending on your current branch)
  5. Apply the security update during a planned maintenance window
  6. Verify the update was applied successfully by checking the version in the console
  7. Test critical functionality to ensure the update did not break existing workflows
  8. Confirm the vulnerability is remediated by reviewing applied patches
Caveat Review Ivanti compatibility documentation; major version upgrades may require migration planning and could have configuration changes

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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