dbcve.org
AvalancheApplication · Ivanti

CVE-2024-24996

CRITICAL · 9.8 CVSS v3.1 Published 2024-04-19
Fix available
A fix is available. Upgrade to 6.4.3.528 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Heap overflow vulnerability in WLInfoRailService component of Ivanti Avalanche before 6.4.3 allows an unauthenticated remote attacker to execute arbitrary commands.

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 heap overflow vulnerability exists in the WLInfoRailService component of Ivanti Avalanche versions prior to 6.4.3. The memory corruption flaw allows an unauthenticated remote attacker to overflow heap memory and achieve arbitrary command execution on the affected system.

MitigationUpgrade Ivanti Avalanche to version 6.4.3 or later. If immediate patching is not feasible, restrict network access to the Avalanche server and consider disabling the WLInfoRailService if feasible.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 if Ivanti Avalanche is installed
    Look for Ivanti Avalanche installation directories (commonly in C:\Program Files\Ivanti or C:\Program Files (x86)\Ivanti on Windows, or /opt/ivanti on Linux). Check for Avalanche-related services and binaries.
    Affected if Ivanti Avalanche software is found on the system
  2. Determine the installed Avalanche version
    Locate the Avalanche version information - typically found in the application's About dialog, version file, or registry keys (HKLM\SOFTWARE\Ivanti\Avalanche\Version on Windows). Compare the full version number against 6.4.3.528.
    Affected if Installed version is lower than 6.4.3.528 (e.g., 6.4.2.x, 6.4.1.x, 6.3.x, etc.)
  3. Verify WLInfoRailService component status
    Check if the WLInfoRailService is running or enabled. On Windows, use Services.msc or 'sc query WLInfoRailService' command. On Linux, check for the service process in running services or configuration files.
    Affected if WLInfoRailService is installed and running as an active service
  4. Assess network exposure of the Avalanche server
    Review firewall rules and network configuration to determine if the Avalanche server ports (typically 80, 443, or custom Avalanche ports) are exposed to untrusted networks or the internet. Use 'netstat -an' or port scanning tools to identify listening interfaces.
    Affected if The Avalanche server is reachable from untrusted/networked endpoints without proper access restrictions

The system is affected if Ivanti Avalanche is installed with a version lower than 6.4.3.528 and the WLInfoRailService component is active 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. If immediate patching is not feasible, restrict network access to the Avalanche server and consider disabling the WLInfoRailService if feasible.

Recommended fix High confidence

Ivanti Avalanche 6.4.3.528 or later

  1. 1. Backup the current Ivanti Avalanche installation and database
  2. 2. Download Ivanti Avalanche version 6.4.3.528 or later from the official Ivanti portal
  3. 3. Stop the Avalanche services, including WLInfoRailService
  4. 4. Install the upgrade following the standard Ivanti upgrade documentation
  5. 5. Verify the WLInfoRailService component is running correctly
  6. 6. Confirm the upgrade was successful by checking the Avalanche version in the admin console
Caveat Review Ivanti release notes for any configuration or migration requirements between versions

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

Fix this in Avalanche Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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