dbcve.org
AvalancheApplication · Ivanti

CVE-2024-27975

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
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
An Use-after-free vulnerability in WLAvalancheService 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 use-after-free vulnerability in the WLAvalancheService component of Ivanti Avalanche versions prior to 6.4.3 allows a remote authenticated attacker to free memory prematurely and then reference that freed memory, leading to arbitrary command execution with SYSTEM-level privileges.

MitigationUpgrade Ivanti Avalanche to version 6.4.3 or later to remediate the use-after-free vulnerability in WLAvalancheService.

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. Verify Ivanti Avalanche is installed
    Check for the presence of the Ivanti Avalanche installation directory (typically C:\Program Files\Ivanti\Avalanche or C:\Program Files (x86)\Ivanti\Avalanche) or look for the WLAvalancheService in Windows Services (services.msc).
    Affected if Ivanti Avalanche is installed and the WLAvalancheService component exists
  2. Identify the installed Ivanti Avalanche version
    Locate the Avalanche software version. Common paths: C:\Program Files\Ivanti\Avalanche\Avalanche.exe or check the version property of the executable file, or look in the Windows Registry under HKLM\SOFTWARE\Wow6432Node\LanDesk\ManageOn The Spot\Path or similar Ivanti registry keys.
    Affected if The installed version is less than 6.4.3.528 or cannot be determined to be 6.4.3.528 or higher
  3. Confirm WLAvalancheService is running
    Open Services (services.msc) and locate the WLAvalancheService, or run 'sc query WLAvalancheService' via command prompt to check service status.
    Affected if WLAvalancheService is installed and running on the system
  4. Verify version against affected range
    Compare the identified version number to the affected range: any version prior to 6.4.3.528 (e.g., 6.4.2, 6.4.1, 6.3.x, etc.) is vulnerable. Versions 6.4.3.528 and later are not affected.
    Affected if The installed version is below 6.4.3.528

The system is affected if Ivanti Avalanche with WLAvalancheService is installed and the installed version is lower than 6.4.3.528.

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 the use-after-free vulnerability in WLAvalancheService.

Recommended fix High confidence

6.4.3.528 or later

  1. Download Ivanti Avalanche version 6.4.3.528 or later from the official Ivanti support portal
  2. Create a backup of the current Avalanche configuration and database
  3. Stop all Avalanche services including WLAvalancheService
  4. Install the updated Avalanche 6.4.3.528 package following standard upgrade procedures
  5. Restart Avalanche services and verify the WLAvalancheService component is running
  6. Confirm the upgrade was successful by checking the installed version in the Avalanche admin console
Caveat Review Ivanti release notes for any configuration changes or migration requirements between your current version and 6.4.3

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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