dbcve.org
AvalancheApplication · Ivanti

CVE-2024-24999

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 traverse directory structures and execute arbitrary commands with SYSTEM-level privileges.

MitigationUpgrade Ivanti Avalanche to version 6.4.3 or later to patch the path traversal vulnerability. If immediate patching is not possible, restrict network access to the Avalanche web component and enforce strict authentication 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
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
    Check for Ivanti Avalanche installation directories or use system inventory tools to locate the product. Common locations include C:\Program Files\Ivanti or /opt/ivanti on Windows and Linux systems respectively.
    Affected if Ivanti Avalanche software is found on the system
  2. Determine installed version
    Locate and read the version information file or use the product's built-in about/version command. Compare the version number against 6.4.3.528.
    Affected if Installed version is lower than 6.4.3.528 (e.g., 6.4.2.x, 6.4.1.x, etc.)
  3. Verify web component is enabled
    Check if the Avalanche web component service is running. On Windows, use Services.msc or sc query. On Linux, check for the Avalanche web service process.
    Affected if The Avalanche web component service is running or enabled
  4. Check network accessibility of web component
    Review firewall rules, web server configuration, and network binding settings to determine if the Avalanche web interface is exposed to network access.
    Affected if The web component is accessible over the network (not localhost-only or blocked)
  5. Confirm authentication status
    Review user account and authentication configuration for the Avalanche web portal to determine if default or weak credentials are in use.
    Affected if Web component authentication is enabled and a valid user account exists (authentication is required for exploitation)

You are affected if Ivanti Avalanche is installed with a version lower than 6.4.3.528, the web component is running and network-accessible, and valid authentication credentials exist.

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. If immediate patching is not possible, restrict network access to the Avalanche web component and enforce strict authentication controls.

Recommended fix High confidence

Ivanti Avalanche 6.4.3.528 or latest stable release

  1. Obtain Ivanti Avalanche version 6.4.3.528 or later from the official Ivanti download portal or support channels
  2. Create a complete backup of the current Avalanche configuration and database
  3. Review Ivanti upgrade documentation for version 6.4.3 to ensure compatibility with your environment
  4. Stop the Avalanche services before performing the upgrade
  5. Install version 6.4.3.528 or the latest stable release
  6. Restart Avalanche services and verify the application is running correctly
  7. Confirm the path traversal vulnerability is resolved by verifying the web component responds normally
  8. Validate that existing functionality works as expected post-upgrade
Caveat Review Ivanti release notes for version 6.4.3 for any configuration or feature changes that may impact existing deployments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Avalanche Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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