dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2024-13162

HIGH · 7.2 CVSS v3.1 Published 2025-01-14
Fix available
A fix is available. Upgrade to 2022 or later.
See remediation →
78/100
Remediation priority · High
High EPSS 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 EPM before the 2024 January-2025 Security Update and 2022 SU6 January-2025 Security Update allows a remote authenticated attacker with admin privileges to achieve remote code execution. This CVE addresses incomplete fixes from CVE-2024-32848.

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 EPM allows a remote authenticated attacker with admin privileges to achieve remote code execution. This CVE represents incomplete fixes from CVE-2024-32848, indicating the original patch did not fully address the SQL injection vector.

MitigationApply the January-2025 Security Update for both the 2024 branch and the 2022 SU6 branch of Ivanti EPM. Restrict admin access to essential personnel only and monitor for suspicious 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 EPM version
    Access the Ivanti Endpoint Manager console, navigate to Help > About, or check the installed software version on the core server via the Windows Programs and Features control panel
    Affected if The installed version is 2022, 2024, or any version lower than 2022 (e.g., 2021, 2020)
  2. Confirm core server version via command line
    Run 'winrm i get http://schemas.microsoft.com/wbem/wsman/1/config/service' or check the EPM installer log files typically located in C:\ProgramData\LANDesk\logs\
    Affected if The reported version matches < 2022, = 2022, or = 2024
  3. Verify admin access configuration
    Check the local administrators group on the EPM core server and confirm which domain/user accounts have Administrator privileges via Computer Management > Local Users and Groups > Groups
    Affected if Any non-administrator or unauthorized user has been granted admin-level privileges to the EPM console
  4. Review SQL database configuration
    Connect to the Microsoft SQL Server instance hosting the EPM database (typically named LANDESK or LDMS) and query the current user roles: SELECT name, type_desc FROM sys.database_principals WHERE type = 'R'
    Affected if The database contains custom or unexpected principal accounts with elevated permissions indicating potential exploitation

Your environment is affected if the installed Ivanti Endpoint Manager version is 2022, 2024, or any version prior to 2022 and the application is accessible to authenticated admin users.

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 January-2025 Security Update for both the 2024 branch and the 2022 SU6 branch of Ivanti EPM. Restrict admin access to essential personnel only and monitor for suspicious SQL query patterns.

Recommended fix High confidence

Ivanti EPM 2024: 2024 January-2025 Security Update; Ivanti EPM 2022: 2022 SU6 January-2025 Security Update

  1. 1. Identify the current version of Ivanti Endpoint Manager (EPM) by checking the console or system information
  2. 2. For Ivanti EPM 2024: Upgrade to the 2024 January-2025 Security Update or later
  3. 3. For Ivanti EPM 2022: Upgrade to 2022 SU6 January-2025 Security Update or later
  4. 4. For versions older than 2022: Upgrade to a supported version (2022 SU6 or 2024) with the January-2025 Security Update applied
  5. 5. After upgrading, verify the SQL injection vulnerability is resolved by reviewing release notes and confirming the CVE is addressed
  6. 6. Test the upgrade in a non-production environment before deploying to production
Caveat Ensure compatibility with existing integrations and test thoroughly in staging environment before production deployment

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 / QA4.0 h
22.0 hours of engineering $3,860
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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