dbcve.org
AvalancheApplication · Ivanti

CVE-2024-27977

HIGH · 8.1 CVSS v3.1 Published 2024-04-19
Fix available
A fix is available. Upgrade to 6.4.3.528 or later.
See remediation →
87/100
Remediation priority · High
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 delete arbitrary files, thereby leading to Denial-of-Service.

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 manipulate file paths using '../' sequences to delete arbitrary files on the system, resulting in denial-of-service conditions.

MitigationUpgrade Ivanti Avalanche to version 6.4.3 or later to patch the path traversal vulnerability. Prior to upgrade, ensure proper backups and plan maintenance window for the enterprise MDM platform.

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
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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
    Look for Ivanti Avalanche installation directory, check Windows Services or Linux init scripts for 'Avalanche' service, or query the MDM platform's web interface.
    Affected if Ivanti Avalanche MDM software is present in the environment
  2. Determine installed version of Ivanti Avalanche
    Access the Avalanche web console and navigate to Help > About, or check the version displayed on the login page. Alternatively, check the installer file name or release notes in the installation directory.
    Affected if The installed version is earlier than 6.4.3.528 (for example, 6.4.2.x, 6.4.1.x, or earlier)
  3. Verify the web component is enabled
    Check if the Avalanche web interface is accessible via HTTP/HTTPS on the configured port (default 80/443 or custom). Confirm the web service is running.
    Affected if The web component is accessible and operational, which is required for the path traversal to be exploitable
  4. Confirm authentication methods are configured
    Review Avalanche user authentication settings in the admin console to confirm user accounts exist and remote access is permitted.
    Affected if Remote authentication is enabled, as the vulnerability requires an authenticated attacker

You are affected if Ivanti Avalanche is installed with a version earlier than 6.4.3.528 and the web component is accessible.

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. Prior to upgrade, ensure proper backups and plan maintenance window for the enterprise MDM platform.

Recommended fix High confidence

6.4.3.528

  1. Obtain Ivanti Avalanche version 6.4.3.528 or later from the official Ivanti download portal at forums.ivanti.com or through your authorized Ivanti support channel
  2. Review the release notes for version 6.4.3.528 to confirm it includes the CVE-2024-27977 path traversal fix
  3. Perform a full backup of the current Avalanche installation, including configuration files and database
  4. Schedule a maintenance window for the upgrade
  5. Upgrade the Ivanti Avalanche installation to version 6.4.3.528 or later
  6. Verify the upgrade was successful by checking the web component responds normally
  7. Confirm the version number in the About or System Information page reflects 6.4.3.528 or higher

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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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