dbcve.org
AvalancheApplication · Ivanti

CVE-2024-24994

HIGH · 8.8 CVSS v3.1 Published 2024-04-19
Fix available
A fix is available. Upgrade to 6.4.3.528 or later.
See remediation →
94/100
Remediation priority · Urgent
High EPSS Remotely reachable 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
A Path Traversal vulnerability in web component of Ivanti Avalanche before 6.4.3 allows a remote authenticated attacker to execute arbitrary commands as SYSTEM.

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

A path traversal vulnerability in the web component of Ivanti Avalanche versions prior to 6.4.3 allows an authenticated remote attacker to traverse the file system and execute arbitrary commands with SYSTEM privileges on the affected Windows server.

MitigationUpgrade Ivanti Avalanche to version 6.4.3 or later to remediate this vulnerability. If immediate patching is not possible, restrict network access to the Avalanche web component to trusted users only.

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
AvalancheApplication
Affected:< 6.4.3.528

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 Ivanti Avalanche installation
    Locate Ivanti Avalanche on the Windows server. Common installation paths include C:\Program Files\Ivanti\Avalanche or C:\Program Files (x86)\Ivanti\Avalanche. Check Programs and Features (Add/Remove Programs) for Ivanti Avalanche listing.
    Affected if Ivanti Avalanche is not installed on the system.
  2. Determine installed Avalanche version
    Open the Windows Registry editor and navigate to HKLM\SOFTWARE\Ivanti\Avalanche\CurrentVersion (or check version info in the Avalanche installation directory). Alternatively, right-click the Avalanche executable and select Properties > Details to view the File Version.
    Affected if The installed version is lower than 6.4.3.528 (for example, 6.4.2.x or earlier).
  3. Verify web component is enabled
    Check if the Avalanche web server service (AvalancheWebServer or similar) is running. Open Services.msc and look for Ivanti Avalanche Web Component or check the Avalanche administration console for web server status.
    Affected if The Avalanche web component service is running and accessible.
  4. Confirm Windows server environment
    Verify the operating system is Windows Server. Run 'systeminfo' in Command Prompt or check System Properties. The CVE specifically affects Windows servers.
    Affected if The affected system is a Windows server running Ivanti Avalanche.
  5. Check web interface accessibility
    Determine if the Avalanche web interface is network-accessible. Check Windows Firewall rules or external network exposure. Attempt to access the Avalanche web portal URL (typically port 8080 or 8443) from a non-localhost client if authorized.
    Affected if The Avalanche web interface is accessible from untrusted networks and the version is below 6.4.3.528.

The environment is affected if Ivanti Avalanche version 6.4.3.528 or higher is NOT installed on a Windows server, and the Avalanche web component is enabled and accessible.

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 6.4.3.528 or later
Fixed in 6.4.3.528
Interim mitigation

Upgrade Ivanti Avalanche to version 6.4.3 or later to remediate this vulnerability. If immediate patching is not possible, restrict network access to the Avalanche web component to trusted users only.

Recommended fix High confidence

Ivanti Avalanche 6.4.3.528 or later

  1. 1. Back up the current Ivanti Avalanche installation and database before proceeding with the upgrade.
  2. 2. Download Ivanti Avalanche version 6.4.3.528 or later from the official Ivanti download portal at forums.ivanti.com or through your Ivanti customer account.
  3. 3. Stop all Avalanche services to ensure a clean upgrade process.
  4. 4. Run the installer for version 6.4.3.528 following the standard upgrade procedure documented in the Ivanti Avalanche installation guide.
  5. 5. After installation completes, verify the version number matches 6.4.3.528 or higher in the Avalanche administration console.
  6. 6. Restart all Avalanche services and confirm the web component is operational.
  7. 7. Validate that the path traversal vulnerability is no longer exploitable by reviewing that file access is properly restricted in the web component.
Caveat Review Ivanti release notes for this version for any configuration or feature changes that may impact existing deployments

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

Fix this in Avalanche Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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