dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2024-13171

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
Insufficient filename validation 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

Insufficient filename validation in Ivanti Endpoint Manager (EPM) allows a remote unauthenticated attacker to achieve remote code execution through malicious file names, but exploitation requires local user interaction.

MitigationApply the January-2025 Security Update (or 2022 SU6 January-2025 Security Update for legacy versions) to remediate the filename validation vulnerability in Ivanti EPM.

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
    Locate the Ivanti Endpoint Manager installation on the system. Common installation paths include C:\Program Files\Ivanti\Endpoint Manager or C:\Program Files (x86)\Ivanti\Endpoint Manager. Check Programs and Features (Add/Remove Programs) for 'Ivanti Endpoint Manager' or 'Ivanti EPM'.
    Affected if Ivanti Endpoint Manager software is present on the system
  2. Identify the installed version of Ivanti EPM
    Check the version by opening the Ivanti Endpoint Manager console and navigating to Help > About, or locate the version information in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\LANDesk\ManageSuite\Setup or within the installation directory's version.xml or similar version file.
    Affected if The exact version number cannot be determined or the version falls within the affected ranges
  3. Compare installed version against affected ranges
    The affected versions are: any version prior to 2022, version 2022 (all updates), and version 2024 (all updates). Compare your identified version number against these ranges. Note that versions after 2024 (such as 2025 and later) are NOT affected.
    Affected if The installed version matches '2022', '2024', or is numerically lower than '2022' (for example, 2021, 2020, etc.)
  4. Assess network exposure of the EPM server
    Determine if the Ivanti Endpoint Manager server is accessible from external networks. Check firewall rules, VPN configuration, and whether the EPM core server (typically ports 80, 443, or 8080/8443) is exposed to untrusted networks. The vulnerability allows remote unauthenticated attackers to exploit the filename validation issue.
    Affected if The EPM server is reachable from untrusted or external networks without proper network segmentation or authentication barriers

The environment is affected if Ivanti Endpoint Manager is installed and the version matches 2022, 2024, or any version older than 2022.

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 (or 2022 SU6 January-2025 Security Update for legacy versions) to remediate the filename validation vulnerability in Ivanti EPM.

Recommended fix Moderate confidence

January-2025 Security Update (2022 SU6 for version 2022, January-2025 for version 2024)

  1. Obtain the January-2025 Security Update for Ivanti Endpoint Manager from the Ivanti portal or official support channels
  2. For Ivanti EPM 2022: Apply the SU6 January-2025 Security Update
  3. For Ivanti EPM 2024: Apply the January-2025 Security Update
  4. Verify the patch was applied successfully by checking the EPM version/build number
  5. Confirm the filename validation vulnerability is remediated by reviewing release notes or consulting Ivanti KB
Caveat Security updates typically have minimal breaking changes; test in non-production environment first

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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