dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 31 Mar 2025.
Endpoint ManagerApplication · Ivanti

CVE-2024-13160

HIGH · 7.5 CVSS v3.1 Published 2025-01-14
Fix available
A fix is available. Upgrade to 2022 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges 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
Absolute path traversal in Ivanti EPM before the 2024 January-2025 Security Update and 2022 SU6 January-2025 Security Update allows a remote unauthenticated attacker to leak sensitive information.

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

Absolute path traversal vulnerability in Ivanti Endpoint Manager (EPM) allows a remote unauthenticated attacker to access sensitive files by manipulating path references to traverse beyond the intended directory structure, enabling information disclosure.

MitigationApply the January-2025 Security Update for Ivanti EPM (both the current version and 2022 SU6) to address the path traversal vulnerability.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 installation
    Check for Ivanti EPM installation by looking in Program Files for 'Ivanti' folder, or check Windows Services for 'Ivanti Endpoint Manager' service, or check IIS for EPM web application pools
    Affected if Ivanti EPM software is present on the server
  2. Identify installed EPM version
    Check the version by examining the 'CoreServer' or 'ServerConfig.xml' file in the Ivanti installation directory, typically found in C:\Program Files\Ivanti\EndpointManager\, or check the Windows Programs and Features list
    Affected if Installed version is 2024 (any patch level) or 2022 (any patch level) or versions prior to 2022
  3. Verify EPM web component is running
    Check if the Core Server web service is running by examining IIS Manager for 'LANDESK' or 'Ivanti' application pools, or check if port 80/443 listeners are active for EPM
    Affected if EPM web interface is accessible and accepting HTTP/HTTPS requests
  4. Review HTTP access logs for path traversal patterns
    Examine IIS or EPM access logs in the Endpoint Manager\logs directory for unusual requests containing '..\' or '..%2F' patterns pointing to system directories like Windows\System32 or etc
    Affected if Log entries show path traversal attempts accessing sensitive system files outside the web root

Environment is affected if Ivanti Endpoint Manager version 2024 or 2022 (or earlier) is installed and its web component is accessible, as these versions contain the path traversal vulnerability allowing unauthenticated file access.

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 Ivanti EPM (both the current version and 2022 SU6) to address the path traversal vulnerability.

Recommended fix Moderate confidence

2024 January-2025 Security Update or 2022 SU6 January-2025 Security Update depending on your current version branch

  1. Download the January-2025 Security Update for Ivanti Endpoint Manager 2024 from the Ivanti download portal
  2. Download the SU6 January-2025 Security Update for Ivanti Endpoint Manager 2022 from the Ivanti download portal
  3. Review the associated security advisory for any prerequisites or additional instructions
  4. Apply the appropriate security update to the affected Ivanti EPM installation
  5. Verify the patch was applied successfully by checking the version number or using Ivanti's built-in diagnostics
  6. Confirm the vulnerability is remediated by reviewing release notes or running a vulnerability scan
Caveat Review Ivanti release notes for any configuration or compatibility changes before applying; test in non-production environment first

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

Fix this in Endpoint Manager Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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