dbcve.org
AvalancheApplication · Ivanti

CVE-2024-25000

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
A Path Traversal 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

A path traversal vulnerability in the web component of Ivanti Avalanche before version 6.4.3 allows an authenticated remote attacker to traverse directory paths and execute arbitrary commands with SYSTEM privileges. The vulnerability stems from insufficient input validation in the web interface, enabling attackers to access restricted files and ultimately achieve command execution at the highest privilege level.

MitigationUpgrade Ivanti Avalanche to version 6.4.3 or later. Since the vulnerability requires authentication, enforce least-privilege principles for user accounts and consider network segmentation to limit exposure to the web component.

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. Verify Ivanti Avalanche installation
    Locate Ivanti Avalanche installation directory or service on the system. Check for presence of Avalanche web component files (commonly in C:\Program Files\Ivanti\Avalanche\ or similar paths).
    Affected if Ivanti Avalanche is installed and the web component files are present.
  2. Check installed version
    Inspect the Avalanche version information, typically found in application metadata, about dialog, or version file within the installation directory. Compare the version number to 6.4.3.528.
    Affected if The installed version is lower than 6.4.3.528.
  3. Confirm web component is enabled
    Verify the Avalanche web service is running. Check Windows Services for 'Ivanti Avalanche' or 'AvalancheServer' service, or inspect web server configuration within the Avalanche installation for enabled endpoints.
    Affected if The Avalanche web component service is running or enabled.
  4. Assess web interface accessibility
    Determine if the Avalanche web interface (typically on port 8080 or 443) is accessible from network locations. Check firewall rules and IIS/web server bindings.
    Affected if The web interface is exposed on a network-accessible port.

The environment is affected if Ivanti Avalanche is installed with a version below 6.4.3.528, the web component is enabled, and the web interface is network-accessible to potential attackers who could obtain valid credentials.

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 the vulnerability requires authentication, enforce least-privilege principles for user accounts and consider network segmentation to limit exposure to the web component.

Recommended fix High confidence

Ivanti Avalanche 6.4.3.528

  1. 1. Obtain Ivanti Avalanche version 6.4.3.528 or later from the official Ivanti support portal (forums.ivanti.com or Ivanti Customer Portal)
  2. 2. Review the official Ivanti Avalanche upgrade documentation for version 6.4.3
  3. 3. Create a complete backup of your current Avalanche configuration and database
  4. 4. Stop all Avalanche services before beginning the upgrade
  5. 5. Install version 6.4.3.528 following the official upgrade procedure
  6. 6. Restart Avalanche services and verify the web component is running
  7. 7. Confirm the installed version is 6.4.3.528 or later
Caveat Review Ivanti release notes for any configuration or behavioral changes 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-25000 — 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-25000 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