dbcve.org
AvalancheApplication · Ivanti

CVE-2024-23533

MEDIUM · 6.5 CVSS v3.1 Published 2024-04-19
Fix available
A fix is available. Upgrade to 6.4.3.528 or later.
See remediation →
71/100
Remediation priority · Elevated
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, in certain conditions can allow an authenticated 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 authenticated remote attacker can exploit this to read sensitive information from memory, potentially exposing credentials, session tokens, or other application data.

MitigationUpgrade Ivanti Avalanche to version 6.4.3 or later. Since this requires authentication, ensure compromised credentials are rotated and implement least-privilege access 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 the Ivanti Avalanche installation directory, typically under C:\Program Files\Ivanti\Avalanche or C:\Program Files (x86)\Ivanti\Avalanche on Windows servers. Look for avalanche.exe or WLAvalancheService.exe processes running on the system.
    Affected if Ivanti Avalanche software is present on the system
  2. Identify installed version
    Locate the version information file or check the binary properties. Common paths include the installation directory or check the Windows Registry under HKLM\SOFTWARE\Ivanti\Avalanche for the Version or DisplayVersion value.
    Affected if Version number returned is lower than 6.4.3.528
  3. Verify WLAvalancheService component status
    Check if the WLAvalancheService Windows service is installed and running. Use 'services.msc' or run 'sc query WLAvalancheService' from an elevated command prompt.
    Affected if The service exists and is running on the vulnerable version
  4. Check product build number directly
    If version appears to be 6.4.3.x, verify the exact build number in the About section of the Avalanche admin console, in the executable properties of avalanche.exe, or in the registry key that shows the full version including build/sub-version.
    Affected if Build number is below .528 (e.g., 6.4.3.400)

User is affected if Ivanti Avalanche with WLAvalancheService is installed and the version/build 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. Since this requires authentication, ensure compromised credentials are rotated and implement least-privilege access controls.

Recommended fix Moderate confidence

6.4.3.528 or later

  1. Backup current Ivanti Avalanche configuration and database before initiating upgrade
  2. Download Ivanti Avalanche version 6.4.3.528 or later from the official Ivanti download portal
  3. Stop the WLAvalancheService and related Avalanche services
  4. Install the updated Avalanche version following standard upgrade procedures
  5. Restart WLAvalancheService and verify all Avalanche components are running
  6. Confirm the version upgrade was successful by checking the Avalanche console or about page
Caveat Review Ivanti release notes for any configuration changes or deprecated features in 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
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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