dbcve.org
AvalancheApplication · Ivanti

CVE-2024-24992

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
High EPSS 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

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, or apply vendor-supplied patches; verify the upgrade in a staging environment before production deployment.

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 installation
    Locate the Ivanti Avalanche installation directory, typically under C:\Program Files\Ivanti\Avalanche or C:\Ivanti\Avalanche. Check for the file AvalancheServer.exe or a version information file within the installation folder.
    Affected if The installed version is below 6.4.3.528 (check the file properties or version info in the About section of the Avalanche admin console)
  2. Verify web component is enabled
    Access the Ivanti Avalanche admin console (usually on port 8080 or 443). Navigate to the server configuration or system settings to confirm the web component service is running and accessible.
    Affected if The web component is enabled and exposed on the network (this is required for the path traversal to be exploitable)
  3. Confirm remote authentication is permitted
    Review the web component authentication settings in the admin console under Security or Access Control. Check if remote/external authentication methods (LDAP, Active Directory, or database-based) are configured and enabled.
    Affected if Remote authentication is enabled, allowing external users to authenticate to the web component (this is required for a remote authenticated attacker to exploit the flaw)
  4. Review web component configuration files
    Inspect configuration files in the web component directory (typically in a conf or config subfolder). Look for file path settings, allowed directories, or any path traversal-related configuration entries.
    Affected if Configuration allows arbitrary file path manipulation or lacks proper path validation settings
  5. Audit for unauthorized command execution indicators
    Review system logs (Windows Event Viewer), Avalanche server logs, and web component access logs for suspicious file access patterns or unexpected command executions originating from the web service.
    Affected if Logs show anomalous file access patterns, unexpected system command executions, or privilege escalation activity linked to web component requests

The environment is affected if Ivanti Avalanche version is below 6.4.3.528 AND the web component is accessible with remote authentication enabled, allowing a path traversal attack to achieve SYSTEM-level command execution.

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, or apply vendor-supplied patches; verify the upgrade in a staging environment before production deployment.

Recommended fix Moderate confidence

Ivanti Avalanche 6.4.3 or later (specifically 6.4.3.528 or higher)

  1. 1. Check current Ivanti Avalanche version via administrative console or system information
  2. 2. Schedule maintenance window and create full system backup including database
  3. 3. Download Ivanti Avalanche 6.4.3 or later from official Ivanti download portal
  4. 4. Follow Ivanti upgrade documentation to apply version 6.4.3 or higher
  5. 5. After upgrade, verify version number reflects 6.4.3 or later
  6. 6. Test critical Avalanche functionalities to ensure proper operation
  7. 7. Review system logs for any post-upgrade anomalies
Caveat Review Ivanti release notes for 6.4.3 for any configuration or feature changes that may require adjustment

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
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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