dbcve.org
AvalancheApplication · Ivanti

CVE-2024-23532

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
An out-of-bounds Read vulnerability in WLAvalancheService component of Ivanti Avalanche before 6.4.3 allows an authenticated remote attacker to perform denial of service attacks. In certain conditions this could also lead to remote code execution.

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

An out-of-bounds read vulnerability in the WLAvalancheService component of Ivanti Avalanche allows an authenticated remote attacker to read memory beyond allocated buffers. This can cause denial of service, and under certain conditions may allow remote code execution.

MitigationUpgrade Ivanti Avalanche to version 6.4.3 or later to address this vulnerability.

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. Verify Ivanti Avalanche is installed
    Check for the presence of the Ivanti Avalanche installation directory (commonly in C:\Program Files\Ivanti\Avalanche or C:\Program Files (x86)\Ivanti\Avalanche) or look for the WLAvalancheService in Windows Services.
    Affected if The software is not found in expected locations or the service is absent.
  2. Find the installed version number
    Locate the version information in the Avalanche installation directory, typically in a version file, about dialog, or check the executable properties of the main Avalanche binary. You can also query the Windows Registry under HKLM\SOFTWARE\Ivanti\Avalanche for a Version value.
    Affected if Unable to determine the version from the installation.
  3. Confirm WLAvalancheService component is present
    Open Windows Services (services.msc) and verify that the WLAvalancheService exists and is either running or set to start. Alternatively, check the Avalanche configuration files for WLAvalancheService settings.
    Affected if The WLAvalancheService component is not found or not configured.
  4. Compare version against the affected range
    Compare the installed version number to 6.4.3.528. If the installed version is a minor version below 6.4.3, or is 6.4.3 but below build 528, the system is vulnerable.
    Affected if The installed version is less than 6.4.3.528.

If Ivanti Avalanche is installed with WLAvalancheService present and the version is below 6.4.3.528, the environment is affected by this vulnerability.

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 address this vulnerability.

Recommended fix High confidence

Ivanti Avalanche 6.4.3.528 or later

  1. 1. Check current Ivanti Avalanche version by accessing the admin console or checking the WLAvalancheService component version
  2. 2. Download Ivanti Avalanche version 6.4.3.528 or later from the official Ivanti support portal (forums.ivanti.com)
  3. 3. Back up the current Avalanche configuration and database before upgrading
  4. 4. Stop the WLAvalancheService component
  5. 5. Install the upgrade following Ivanti's standard upgrade procedure for Avalanche
  6. 6. Start the WLAvalancheService component after upgrade completes
  7. 7. Verify the version shows 6.4.3.528 or later and that the service is running properly
Caveat Review Ivanti release notes for any configuration or compatibility changes between your current version and 6.4.3.528 before upgrading

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

Fix this in Avalanche Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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