dbcve.org
AvalancheApplication · Ivanti

CVE-2024-27976

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 filesystem paths 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 to patch the path traversal vulnerability. If immediate patching is not possible, restrict network access to the Avalanche web component and ensure strong authentication controls are in place.

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. Confirm Ivanti Avalanche is installed
    Check for Ivanti Avalanche installation directory, typically in C:\Program Files\Ivanti\Avalanche or C:\Ivanti\Avalanche on Windows, or /opt/ivanti/avalanche on Linux. Look for avalanche.exe, AvalancheServer.exe, or related service entries in Windows Services or Linux service manager.
    Affected if Ivanti Avalanche software is present on the system
  2. Identify installed Avalanche version
    Locate the version information file or check the Avalanche Server application. Common locations: C:\Program Files\Ivanti\Avalanche\AvalancheServer.exe (right-click > Properties > Details tab for File Version), or check the About/Help section within the Avalanche Admin Console. Look for a build/version number.
    Affected if Installed version is lower than 6.4.3.528 or version cannot be determined (treat unknown versions as potentially affected)
  3. Verify web component is accessible
    Check if the Avalanche web interface is running and accessible. Default web port is typically 8080 or 8443. Confirm the web service is listening: run 'netstat -an | findstr 8080' or 'netstat -an | findstr 8443' on Windows, or 'netstat -tlnp | grep -E "8080|8443"' on Linux.
    Affected if Web component is exposed and running (vulnerability requires web component to be accessible)
  4. Check authentication configuration
    Review Avalanche user accounts and authentication settings through the Admin Console. Verify if default or weak credentials exist. Check Windows Event Viewer or Avalanche logs for recent authentication events.
    Affected if Remote authentication is enabled and attacker could obtain valid credentials (vulnerability requires authenticated access)

System is affected if Ivanti Avalanche is installed with version lower than 6.4.3.528 AND the web component is accessible, as the path traversal flaw requires the web interface to be reachable and an authenticated session to exploit.

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 ensure strong authentication controls are in place.

Recommended fix High confidence

Ivanti Avalanche 6.4.3.528

  1. 1. Download Ivanti Avalanche version 6.4.3.528 or later from the official Ivanti download portal
  2. 2. Back up the current Avalanche database and configuration files
  3. 3. Stop the Avalanche server services
  4. 4. Run the installer for version 6.4.3.528
  5. 5. Follow the upgrade wizard prompts, selecting the upgrade option
  6. 6. After installation completes, start the Avalanche server services
  7. 7. Verify the web component is accessible and functioning normally
  8. 8. Confirm the version number shows 6.4.3.528 or later

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
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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