dbcve.org
AvalancheApplication · Ivanti

CVE-2024-23527

HIGH · 7.5 CVSS v3.1 Published 2024-04-25
Fix available
A fix is available. Upgrade to 6.4.3.528 or later.
See remediation →
84/100
Remediation priority · High
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
An out-of-bounds read vulnerability in WLAvalancheService component of Ivanti Avalanche before 6.4.3, in certain conditions can allow an unauthenticated remote attacker to read sensitive information in memory.

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

An out-of-bounds read vulnerability exists in the WLAvalancheService component of Ivanti Avalanche versions prior to 6.4.3. An unauthenticated remote attacker can exploit certain conditions to read sensitive information from memory, potentially exposing credentials, session tokens, or other data in the process memory.

MitigationUpgrade Ivanti Avalanche to version 6.4.3 or later. If immediate patching is not possible, restrict network exposure of the WLAvalancheService to trusted internal networks or implement additional firewall controls.

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
None
Availability
None

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

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 Ivanti Avalanche installation directory, typically in C:\Program Files\Ivanti\Avalanche or C:\Ivanti\Avalanche on Windows servers. Also check Windows Services for 'Avalanche' or 'WLAvalancheService' entries using Services.msc or sc query command.
    Affected if Ivanti Avalanche software is not found on the system, the vulnerability does not apply.
  2. Identify the installed Avalanche version
    Locate the Avalanche version information - common paths include the About dialog within the Avalanche console, or check version metadata in the installation directory files. The version typically appears in the format X.X.X.XXX.
    Affected if Unable to determine version means the check is inconclusive.
  3. Compare version to affected range
    Compare your installed version number to the affected threshold: 6.4.3.528. Any version below 6.4.3.528 falls within the vulnerable range.
    Affected if Installed version is 6.4.3.527 or lower, or any version prior to 6.4.3.528.
  4. Verify WLAvalancheService component status
    Check if the WLAvalancheService Windows service exists and is running. Use Services.msc, or run 'sc query WLAvalancheService' or 'Get-Service WLAvalancheService' in PowerShell.
    Affected if WLAvalancheService is not present or not running, the specific attack surface may be reduced but the software may still be considered vulnerable if version is affected.

You are affected if Ivanti Avalanche is installed with WLAvalancheService present and the installed version is 6.4.3.527 or lower (below 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. If immediate patching is not possible, restrict network exposure of the WLAvalancheService to trusted internal networks or implement additional firewall controls.

Recommended fix Moderate confidence

Ivanti Avalanche 6.4.3.528 or later

  1. 1. Back up your current Ivanti Avalanche configuration and database before proceeding with any upgrade.
  2. 2. Download Ivanti Avalanche version 6.4.3.528 or later from the official Ivanti support portal.
  3. 3. Review Ivanti Avalanche 6.4.3.528 release notes for any specific upgrade prerequisites or instructions.
  4. 4. Stop the WLAvalancheService and related Avalanche services on the server.
  5. 5. Install the upgrade following the standard Ivanti Avalanche upgrade procedure.
  6. 6. Verify the upgrade was successful by checking the WLAvalancheService component version.
  7. 7. Restart Avalanche services and confirm normal operation.
  8. 8. Validate that the out-of-bounds read vulnerability is no longer present.
Caveat Review release notes for any configuration changes or migration requirements between your current version and 6.4.3.528

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

Fix this in Avalanche Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
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,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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