Cyber Resilience

CVE-2024-47011

Path Traversal in Ivanti Avalanche ≤ 6.4.5

Published
08 October 2024
Modified
16 October 2024
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.56 99th percentile
Risk Priority 80 floored blend · peak EPSS

Summary

CVE-2024-47011 is a high-severity Path Traversal (CWE-22) vulnerability in Ivanti Avalanche. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 1% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — 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-47011 is a path traversal vulnerability (CWE-22) present in Ivanti Avalanche prior to version 6.4.5. The flaw allows directory traversal that can expose files outside the intended web root, leading to unauthorized disclosure of sensitive information on affected systems.

A remote unauthenticated attacker can exploit the issue over the network with low attack complexity and no user interaction required. Successful exploitation yields high confidentiality impact while leaving integrity and availability unaffected, consistent with the CVSS 7.5 rating.

The referenced Ivanti security advisory for Avalanche 6.4.5 addresses remediation through an upgrade to that version. The EPSS score is currently 0.5319 with an identical peak value.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Path Traversal in Ivanti Avalanche before version 6.4.5 allows a remote unauthenticated attacker to leak sensitive information

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-32563Same product: Ivanti Avalanche
CVE-2024-24999Same product: Ivanti Avalanche
CVE-2024-13180Same product: Ivanti Avalanche
CVE-2024-27976Same product: Ivanti Avalanche
CVE-2023-41474Same product: Ivanti Avalanche
CVE-2024-27977Same product: Ivanti Avalanche
CVE-2024-38652Same product: Ivanti Avalanche
CVE-2024-24994Same product: Ivanti Avalanche
CVE-2024-24997Same product: Ivanti Avalanche
CVE-2023-28127Same product: Ivanti Avalanche

Affected Assets

ivanti
avalanche
≤ 6.4.5

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V5.3.2

Mitigating Controls (NIST 800-53 r5) AI

Enforces the intended directory access authorizations that path traversal would otherwise bypass.

Input validation directly neutralizes special path elements before pathname construction occurs.

Least privilege reduces the impact of any unauthorized file access obtained via traversal.

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.

PR.PS-02 partial match
prevents

Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.

PR.AA-05 none match
prevents

PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.

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.

finds

Security testing in development catches path traversal via static/dynamic analysis.

prevents

Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.

prevents

Application security requirements include rules for safe file handling and canonicalization.

prevents

Secure architecture principles require least-privilege file access and directory isolation.

prevents

Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.

mitigates

Information access restriction limits which files an application may read or write.

References