dbcve.org
AvalancheApplication · Ivanti

CVE-2024-24995

HIGH · 7.5 CVSS v3.1 Published 2024-04-19
Fix available
A fix is available. Upgrade to 6.4.3.528 or later.
See remediation →
81/100
Remediation priority · High
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 Race Condition (TOCTOU) 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 · moderate confidence

A Time-of-Check-to-Time-of-Use (TOCTOU) race condition vulnerability exists in the web component of Ivanti Avalanche prior to version 6.4.3. This flaw allows a remote, authenticated attacker to exploit a race window between security state checks and command execution, enabling arbitrary command execution with SYSTEM privileges.

MitigationUpgrade Ivanti Avalanche to version 6.4.3 or later to remediate this vulnerability. As this allows SYSTEM-level command execution, priority should be given to patching any exposed instances.

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

CVSS:3.1/AV:N/AC:H/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. Confirm Ivanti Avalanche is installed
    Check for the presence of Ivanti Avalanche installation directory, typically found at C:\Program Files\Ivanti\Avalanche\ or look for the Avalanche service in Windows Services (services.msc)
    Affected if Ivanti Avalanche is found installed on the system
  2. Identify installed Ivanti Avalanche version
    Check the version information of the AvalancheWnS.exe or AvalancheServer.exe binary in the installation directory, or view the product version in Windows Programs and Features (Add/Remove Programs)
    Affected if The displayed version is earlier than 6.4.3.528
  3. Check web component status
    Examine if the Avalanche web console is accessible by attempting to reach the web interface on default ports (typically port 80 or 443, or port 8080/8443 for non-default installations)
    Affected if The web interface responds and accepts authentication
  4. Verify remote access is enabled
    Review the Avalanche server configuration for remote management access settings, typically found in the server configuration files or registry entries controlling web service bindings
    Affected if Remote management access is permitted on accessible network interfaces
  5. Confirm authentication is configured
    Check whether local or domain user authentication is enabled for the Avalanche web console, which can be verified through the web interface login page or server configuration
    Affected if User authentication is enabled for the web component

The environment is affected if Ivanti Avalanche is installed with a version lower than 6.4.3.528 and the web component is accessible for remote authenticated users.

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. As this allows SYSTEM-level command execution, priority should be given to patching any exposed instances.

Recommended fix Moderate confidence

Ivanti Avalanche 6.4.3.528 or later

  1. 1. Back up the current Ivanti Avalanche installation and database before proceeding with any upgrade.
  2. 2. Download Ivanti Avalanche version 6.4.3.528 or later from the official Ivanti download portal at forums.ivanti.com or the Ivanti Customer Portal.
  3. 3. Stop the Avalanche services to ensure a clean upgrade process.
  4. 4. Install the upgraded Avalanche 6.4.3.528 version following the standard upgrade procedures documented in the Ivanti Avalanche Administration Guide.
  5. 5. Verify the upgrade was successful by checking the Avalanche version in the administration console.
  6. 6. Validate that the web component is functioning correctly and that the TOCTOU vulnerability has been addressed.
  7. 7. After upgrade, ensure all remote authenticated users have appropriate access controls as this vulnerability allowed authenticated attackers to execute arbitrary commands.
Caveat Review Ivanti Avalanche 6.4.3 release notes for any configuration or feature changes that may require adjustment in 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
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
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,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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