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

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 remote unauthenticated attackers to access files outside the web root directory by manipulating file paths in HTTP requests. The vulnerability affects versions prior to the January-2025 Security Update for both the 2024 release and 2022 SU6 release, enabling sensitive information disclosure.

MitigationApply the January-2025 Security Update for Ivanti EPM (both 2024 and 2022 SU6 versions) to address the path traversal vulnerability. Restrict network exposure of affected systems until patched.

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 Protection Manager is installed
    Check for the 'Ivanti Endpoint Protection Manager' service in Windows Services or look for the EPM management console application on the server
    Affected if The product is present on the system
  2. Identify the installed EPM version
    Access the EPM management console and navigate to Help > About, or check the installed programs list in Windows Control Panel to find the exact version number
    Affected if The version is 2022 (any release) or 2024 (any release) without the January-2025 security update applied
  3. Verify the patch status
    Check if the January-2025 Security Update has been applied by reviewing the installed updates or the EPM version (2022 SU6 or 2024 with Jan-2025 patch)
    Affected if The January-2025 update is not present and the version matches 2022 or 2024
  4. Assess network exposure of the management interface
    Determine if the EPM management console (typically on ports 8080 or 443) is accessible from untrusted networks by reviewing firewall rules or network configuration
    Affected if The management interface is exposed to the internet or untrusted networks without IP restrictions

The environment is affected if Ivanti Endpoint Protection Manager is installed with version 2022 or 2024 and the January-2025 Security Update has not been applied, especially if the management interface is network-accessible.

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 2024 and 2022 SU6 versions) to address the path traversal vulnerability. Restrict network exposure of affected systems until patched.

Recommended fix Moderate confidence

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

  1. Identify the current version of Ivanti Endpoint Manager (EPM) by checking the console or system information
  2. If running version 2024, download and apply the January-2025 Security Update from Ivanti's support portal
  3. If running version 2022, download and apply the SU6 January-2025 Security Update from Ivanti's support portal
  4. After applying the update, verify the patch was successfully installed by checking the EPM version information
  5. Confirm the path traversal vulnerability is remediated by reviewing system logs for any attempted exploitation attempts

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

Fix this in Endpoint Manager Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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