dbcve.org
AvalancheApplication · Ivanti

CVE-2024-24998

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 a remote authenticated attacker to manipulate file paths and execute arbitrary commands with SYSTEM-level privileges.

MitigationUpgrade Ivanti Avalanche to version 6.4.3 or later to patch the path traversal vulnerability in 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. Identify if Ivanti Avalanche is installed
    Locate Ivanti Avalanche installation directory or check for the Avalanche service on the system. Common locations include C:\Program Files\Avalanche or C:\Inetpub\wwwroot\Avalanche. Verify the Avalanche Windows service is present in Services.msc.
    Affected if Ivanti Avalanche software is found installed on the system
  2. Check installed Ivanti Avalanche version
    Navigate to the installation directory and locate the version information file (often version.txt, or check file properties of the main executable). Alternatively, access the Avalanche web interface and check the About or version page typically found at /Avalanche/about.do or /Avalanche/welcome.do.
    Affected if The installed version is lower than 6.4.3.528 (e.g., 6.4.2, 6.4.1, 6.3.x, etc.)
  3. Verify web component accessibility
    Confirm the Avalanche web component is running by accessing the web interface URL (typically http://localhost/Avalanche or https://localhost/Avalanche). Check if the IIS application pool or embedded web server is running.
    Affected if The Avalanche web interface is accessible (responds to HTTP/HTTPS requests)
  4. Confirm authentication method in use
    Review the web component configuration to determine if remote authentication is enabled. Check if the web service allows remote connections and what authentication mechanisms are configured in the Avalanche administration console.
    Affected if Remote authenticated access to the web component is permitted

The environment is affected if Ivanti Avalanche version 6.4.3.528 or higher is NOT installed AND the Avalanche web component is accessible remotely or to authenticated users.

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 patch the path traversal vulnerability in the web component.

Recommended fix Moderate confidence

Ivanti Avalanche 6.4.3.528 or later

  1. 1. Back up the current Ivanti Avalanche installation, including configuration files and database.
  2. 2. Download Ivanti Avalanche version 6.4.3.528 or later from the official Ivanti download portal (forums.ivanti.com or Ivanti Customer Portal).
  3. 3. Stop the Ivanti Avalanche service completely before applying the update.
  4. 4. Apply the upgrade to the Avalanche server following the standard Ivanti upgrade procedure.
  5. 5. Verify the upgrade was successful by checking the version number in the Avalanche administration console.
  6. 6. Restart the Avalanche service and confirm all components are running properly.
  7. 7. Validate that the path traversal vulnerability is no longer exploitable by reviewing system logs for any suspicious file access attempts.
Caveat Standard upgrade - review Ivanti release notes for any configuration 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
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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