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

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 sensitive files on the underlying filesystem by supplying absolute file paths in HTTP requests, potentially exposing configuration data, credentials, or other system files.

MitigationApply the January-2025 Security Update for the relevant Ivanti EPM version (2024 or 2022 SU6) to remediate 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. Identify the installed Ivanti EPM version
    Access the EPM console or check the product information page (typically via Help > About or the installer properties). Alternatively, check the registry or installation directory for version metadata.
    Affected if The installed version is 2022, 2024, or any version lower than 2022 (e.g., 2021, 2020). These versions fall within the affected range.
  2. Determine if the EPM web services are internet-facing
    Review firewall rules, load balancer configurations, or VPN settings to confirm whether the EPM web interface (typically on ports 80/443 or custom ports) is exposed to the public internet or untrusted networks.
    Affected if The web interface or API endpoints are directly accessible from untrusted networks without authentication protection.
  3. Inspect access logs for suspicious path traversal requests
    Examine EPM web server logs (IIS logs, Apache logs, or EPM-specific logs) for unusual patterns such as requests containing '../', '..\', or absolute paths like '/etc/passwd' or 'C:\Windows\'.
    Affected if Logs contain path traversal patterns or requests attempting to access system files outside the web root directory.
  4. Verify authentication is enforced on all endpoints
    Test accessing common EPM endpoints (such as /Servlets/..., /API/..., or other known paths) without providing credentials to confirm they require authentication.
    Affected if Any endpoint permits unauthenticated access to file resources or returns sensitive data without a login prompt.

A user is affected if their Ivanti EPM installation is version 2022, 2024, or any version prior to 2022, and the vulnerable web component is accessible without authentication.

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 the relevant Ivanti EPM version (2024 or 2022 SU6) to remediate the path traversal vulnerability.

Recommended fix Moderate confidence

2022 SU6 January-2025 Security Update (for 2022) or 2024 January-2025 Security Update (for 2024 and later)

  1. Identify your current Ivanti Endpoint Manager version by checking the administration console or system information
  2. For versions 2022: Apply the '2022 SU6 January-2025 Security Update'
  3. For versions 2024 and later: Apply the '2024 January-2025 Security Update'
  4. After applying the update, verify the patch was successfully installed by checking the version number in the administration console
  5. Confirm the vulnerability is remediated by reviewing the patch notes or consulting Ivanti KB articles
Caveat Standard EPM update procedures should apply; test in non-production environment before deploying to production

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

Fix this in Endpoint Manager Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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