Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-13161 is a critical-severity Absolute Path Traversal (CWE-36) vulnerability in Ivanti Endpoint Manager. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); ranked in the top 0.2% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-13161 is an absolute path traversal vulnerability, tracked under CWE-36, that affects Ivanti Endpoint Manager (EPM) prior to the 2024 January-2025 Security Update and the 2022 SU6 January-2025 Security Update. The flaw permits remote, unauthenticated access to arbitrary files on the affected system, resulting in disclosure of sensitive information and carrying a CVSS 3.1 base score of 9.8.
A remote attacker with no credentials or user interaction can send crafted requests that traverse the filesystem and retrieve protected data. Successful exploitation can lead to full compromise of confidentiality, integrity, and availability on the target EPM instance.
Ivanti’s January 2025 security advisory directs customers to apply the listed updates for both EPM 2024 and EPM 2022 SU6 branches. The vulnerability is also listed in CISA’s Known Exploited Vulnerabilities catalog, confirming active exploitation in the wild. The associated EPSS score has reached a peak of 0.9271 with a current value of 0.9177, indicating sustained attacker interest.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-51387
Vulnerability Data
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.
- CWE(s)
- KEV Date Added
- 10 March 2025
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Input validation directly stops construction of absolute paths from untrusted data before they reach file operations.
Enforced access authorizations can limit which resources are reachable even if a traversal succeeds.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input validation and path sanitization that prevent absolute path traversal.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
A.8.25 mandates secure SDLC practices (secure requirements, checkpoints, secure coding guidelines, testing including code scans/penetration tests) that reach many path-traversal instances in custom software, but leaves a bounded remainder (e.g. third-party components, misconfigured outsourced development, or incomplete enforcement of guidelines) where the weakness can still be introduced and exploited.
Application security requirements typically mandate controls against path traversal in file-access functions.
A.8.27 mandates security-by-design principles (least privilege, default-deny, distrust-external-input, hardening, design review against attack patterns) that reach a minority slice of absolute path traversal (e.g. explicit path canonicalization rules or sandboxing), but most instances arise from ordinary string-concatenation flaws in custom code that the clause's high-level engineering principles do not themselves stop from being written or exploited.
Secure coding standards directly require neutralization of absolute path sequences in pathname construction.
Security testing in development can detect absolute path traversal via static analysis and fuzzing.