What is the CVSS score of CVE-2024-13179?

CVE-2024-13179 has a CVSS 3.1 base score of 7.3 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L. EPSS exploitation probability: 1.0%.

Which versions of Avalanche are affected by CVE-2024-13179?

Organizations using Ivanti Avalanche face moderate risk from CVE-2024-13179, a path traversal vulnerability rated CVSS 7.3.

How to fix or mitigate CVE-2024-13179?

Within 30 days: Identify all affected systems running Ivanti Avalanche and apply vendor patches as part of regular patch cycle. Review file handling controls and restrict upload directories.

Avalanche CVE-2024-13179

HIGH

Path Traversal (CWE-22)

2025-01-14 3c1d8aa1-5a33-4ea4-8992-aadd6440af75

Path Traversal Ivanti Avalanche

7.3

CVSS 3.1

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

Low

Lifecycle Timeline

Analysis Generated

Mar 28, 2026 - 18:03 vuln.today

CVE Published

Jan 14, 2025 - 17:15 nvd

HIGH 7.3

DescriptionNVD

Path Traversal in Ivanti Avalanche before version 6.4.7 allows a remote unauthenticated attacker to bypass authentication.

AnalysisAI

Path Traversal in Ivanti Avalanche before version 6.4.7 allows a remote unauthenticated attacker to bypass authentication. Rated high severity (CVSS 7.3), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.

Technical ContextAI

This vulnerability is classified as Path Traversal (CWE-22), which allows attackers to access files and directories outside the intended path. Path Traversal in Ivanti Avalanche before version 6.4.7 allows a remote unauthenticated attacker to bypass authentication. Affected products include: Ivanti Avalanche. Version information: version 6.4.7.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Validate and canonicalize file paths. Use chroot or sandboxing. Reject input containing path separators or '../' sequences.