dbcve.org
AvalancheApplication · Ivanti

CVE-2024-23529

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 →
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 · high confidence

An out-of-bounds read vulnerability exists in the WLAvalancheService component of Ivanti Avalanche prior to version 6.4.3. This flaw allows an unauthenticated remote attacker to read sensitive information from memory due to improper bounds checking, potentially exposing configuration data, credentials, or other memory-resident secrets.

MitigationUpgrade Ivanti Avalanche to version 6.4.3 or later to remediate this vulnerability. Until the patch is applied, consider network segmentation and restricting access to the WLAvalancheService to minimize exposure.

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 (commonly C:\Program Files\Ivanti\Avalanche or /opt/ivanti/avalanche) or look for Avalanche services in Windows Services or Linux service listings
    Affected if Ivanti Avalanche software is present on the system
  2. Identify installed Avalanche version
    Locate the version information - typically in the About dialog within the Avalanche console, or check version files in the installation directory (often found in version.txt, or in the metadata of WLAvalancheService.exe/dll)
    Affected if The installed version is earlier than 6.4.3.528 (or the version cannot be determined)
  3. Verify WLAvalancheService component status
    Check if the WLAvalancheService Windows service (or Unix daemon) is running - in Windows use Services.msc or 'sc query WLAvalancheService', in Linux check process list for avalanche or wlavalanche service
    Affected if WLAvalancheService is installed and running as the vulnerable component
  4. Check network exposure of WLAvalancheService
    Identify the listening port for WLAvalancheService (typically ports 80, 443, or 8080/8443 for the Avalanche web server) using netstat -an or similar network tools, then determine if the service is accessible from untrusted networks
    Affected if The WLAvalancheService port is exposed to unauthenticated/untrusted network access without proper firewall restrictions

If Ivanti Avalanche is installed with a version earlier than 6.4.3.528 AND the WLAvalancheService component is active, the environment is vulnerable to unauthenticated memory read attacks via network exposure.

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. Until the patch is applied, consider network segmentation and restricting access to the WLAvalancheService to minimize exposure.

Recommended fix Moderate confidence

Ivanti Avalanche 6.4.3.528 or later

  1. Back up the current Ivanti Avalanche installation, configuration files, and database before proceeding
  2. Download Ivanti Avalanche version 6.4.3.528 or later from the official Ivanti support portal (forums.ivanti.com)
  3. Stop the WLAvalancheService and related Avalanche services
  4. Install the upgraded Avalanche version following the standard Ivanti upgrade documentation
  5. Start the Avalanche services and verify the WLAvalancheService component is running
  6. Confirm the installed version is 6.4.3.528 or higher

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

Fix this in Avalanche Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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