Endpoint ManagerApplication · Ivanti

CVE-2024-13172

HIGH · 7.8 CVSS v3.1 Published 2025-01-14
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
Improper signature verification in Ivanti EPM before the 2024 January-2025 Security Update and 2022 SU6 January-2025 Security Update allows a remote unauthenticated attacker to achieve remote code execution. Local 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 · moderate confidence

Improper signature verification in Ivanti Endpoint Manager (EPM) allows a remote unauthenticated attacker to achieve remote code execution. The vulnerability exists in versions prior to the January-2025 Security Updates and requires local user interaction to trigger the attack, suggesting the attacker may need to entice a user into opening a malicious file or initiating a connection.

MitigationApply the January-2025 Security Update for supported versions or the 2022 SU6 January-2025 Security Update for legacy versions. Prioritize patching due to the high-severity rating 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
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. Confirm Ivanti Endpoint Manager is installed
    Check Windows Programs and Features for 'Ivanti Endpoint Manager' or check services list for 'Ivanti Endpoint Manager' or 'LANDesk' services running
    Affected if Ivanti Endpoint Manager is present on the system
  2. Determine the installed EPM version
    Open the EPM console and check About/Version information, or check the Windows registry under HKLM\SOFTWARE\LANDesk\ManageSuite\Setup for version values
    Affected if Version is 2022, 2024, or any version prior to the January-2025 Security Updates
  3. Verify if signature verification is enforced
    Check EPM security settings for code signing and package signature validation configuration, typically found in EPM console under Security or Policy settings
    Affected if Signature verification is disabled or set to permissive mode, allowing unsigned or improperly signed content
  4. Check for recent inbound updates or patches
    Review EPM server logs for any recently imported packages, patches, or updates, especially from untrusted sources
    Affected if Unsigned packages were imported or applied recently without signature validation errors being raised

You are affected if Ivanti Endpoint Manager is installed and the version is 2022, 2024, or any version prior to the January-2025 update, with signature verification disabled or bypassed allowing unsigned content to be processed.

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 supported versions or the 2022 SU6 January-2025 Security Update for legacy versions. Prioritize patching due to the high-severity rating and RCE capability.

Recommended fix Moderate confidence

2024 January-2025 Security Update or 2022 SU6 January-2025 Security Update

  1. Identify the current version of Ivanti Endpoint Manager (EPM) by checking About or system information
  2. For EPM 2024: Apply the 'January-2025 Security Update' to address the improper signature verification vulnerability
  3. For EPM 2022: Apply the '2022 SU6 January-2025 Security Update' to address the improper signature verification vulnerability
  4. After applying the update, verify the version reflects the patched release
  5. Restart the EPM services if required by the update installation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Endpoint Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-13172 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-13172 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