Threats / Ivanti / CVE-2024-13160
CVE-2024-13160
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Ivanti Endpoint Manager (EPM) vulnerability
Ivanti Endpoint Manager contains an absolute path traversal vulnerability allowing unauthenticated remote attackers to access sensitive information through improper file path validation.
Verdict
Today item — known-exploited.
A remote unauthenticated attacker can exploit path traversal in Ivanti EPM to read arbitrary files and leak sensitive data. The high EPSS score and active exploitation in the wild indicate immediate risk to exposed instances.
CISA KEV Yes · 2025-03-105EPSS 0.91004 (verify live)6CVSS 9.83CISA SSVC Exploitation: active · Automatable: yes · Impact: total4Exploit Public PoC / detection · nuclei template13
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
309 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-03-10).
Probability (EPSS)
EPSS 0.91004 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Ivanti, Endpoint Manager (EPM). Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-36 Absolute Path Traversal — weakness family: Path traversal / file.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 55 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a request with absolute path sequences to bypass file access controls in Ivanti EPM.
Business
Sensitive configuration files, credentials, or user data stored on the EPM server become accessible to unauthenticated threat actors.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I extract leaked credentials or authentication tokens from exposed files to escalate access or pivot within the network.
Business
Compromised credentials enable lateral movement, increasing the scope and severity of the breach beyond the EPM application.
3
Lateral reach — past segmentation narrative 3
Attacker
I use disclosed sensitive information to refine targeted attacks against the organization or its endpoints.
Business
Intelligence gathered from path traversal informs follow-on attacks, reducing attacker reconnaissance time and increasing breach likelihood.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05