dbcve.org
AvalancheApplication · Ivanti

CVE-2024-23534

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 Unrestricted File-upload vulnerability in web 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

An unrestricted file upload vulnerability in the web component of Ivanti Avalanche allows a remote authenticated attacker to upload malicious files and execute arbitrary commands with SYSTEM privileges, achieving full remote code execution on the affected server.

MitigationUpgrade Ivanti Avalanche to version 6.4.3 or later. Until patched, restrict network access to the Avalanche web interface and monitor for suspicious file upload requests.

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. Identify Ivanti Avalanche version
    Locate the Avalanche installation directory and check the version information file, or query the Avalanche server status page via the web interface for version details
    Affected if The installed version is lower than 6.4.3.528 (e.g., 6.4.2.x, 6.4.1.x, or earlier)
  2. Confirm web component is accessible
    Verify the Avalanche web interface is reachable on its configured HTTP/HTTPS port (typically 80/443 or custom port)
    Affected if The web component is exposed and accessible to the attacker (authenticated users)
  3. Check for unauthorized file uploads
    Inspect the web upload directories (typically under the Avalanche web root, look for directories like /uploads, /files, /temp) for unexpected executable files (.asp, .aspx, .jsp, .php, .exe, .dll)
    Affected if Suspicious executable files are found in upload directories that were not placed by administrators
  4. Look for web shell artifacts
    Search the web root directory for newly created or modified scripts with suspicious content (e.g., base64-encoded strings, system() calls, cmd= parameters)
    Affected if Unknown scripts or web shells are present in the web directory structure
  5. Review for unexpected system-level execution
    Check running processes on the server for unexpected executables spawned by the web server process (w3wp.exe, inetinfo.exe, or Avalanche-specific service), and review Windows Event Logs for anomalous command executions
    Affected if Commands are being executed under the SYSTEM account from web server processes

You are affected if Ivanti Avalanche version is below 6.4.3.528 AND the web component is accessible to authenticated users, as this allows remote code execution with SYSTEM privileges.

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. Until patched, restrict network access to the Avalanche web interface and monitor for suspicious file upload requests.

Recommended fix High confidence

Ivanti Avalanche 6.4.3.528 or later

  1. 1. Backup the current Ivanti Avalanche installation and database before proceeding
  2. 2. Obtain Ivanti Avalanche version 6.4.3.528 or later from the official Ivanti support portal (forums.ivanti.com)
  3. 3. Stop all Avalanche server services
  4. 4. Install the upgrade following Ivanti's standard upgrade procedures
  5. 5. Verify the installation completed successfully
  6. 6. Restart Avalanche services
  7. 7. Confirm the vulnerability is remediated by verifying the web component accepts only expected file types
Caveat Review Ivanti upgrade documentation for any configuration migration requirements or prerequisites before upgrading

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
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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