dbcve.org
AvalancheApplication · Ivanti

CVE-2024-29848

HIGH · 7.2 CVSS v3.1 Published 2024-05-31
Fix available
A fix is available. Upgrade to 6.4.3.602 or later.
See remediation →
78/100
Remediation priority · High
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
An unrestricted file upload vulnerability in web component of Ivanti Avalanche before 6.4.x allows an authenticated, privileged user 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

An unrestricted file upload vulnerability exists in the web component of Ivanti Avalanche before version 6.4.x. An authenticated, privileged user can upload arbitrary files without proper validation, enabling them to execute commands with SYSTEM-level privileges on the affected Windows system.

MitigationUpdate Ivanti Avalanche to version 6.4.x or later to patch the unrestricted file upload vulnerability. Apply the update during a planned maintenance window following standard change management procedures.

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.602

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Verify Ivanti Avalanche is installed
    Check for Ivanti Avalanche installation directory, typically in Program Files or Program Files (x86), or look for the service in Windows Services (services.msc)
    Affected if Ivanti Avalanche software is present on the system
  2. Identify installed version
    Check the version of Ivanti Avalanche - typically found in the About section of the application, in the installation directory, or via the Windows installer information
    Affected if Installed version is earlier than 6.4.3.602 (e.g., 6.3.x, 6.2.x, etc.)
  3. Confirm web component is enabled
    Check if the Avalanche web server service is running - look for Wavelink Avalanche or similar web service in Windows Services, or check if port 8080/8443 (common Avalanche web ports) are listening
    Affected if The Avalanche web component service is running and accessible
  4. Verify privilege context
    Review user accounts with administrative or privileged access to the Avalanche web interface - check for any authenticated users in the system
    Affected if Any authenticated privileged user account exists in the Avalanche system (the vulnerability requires an authenticated, privileged user)

You are affected if Ivanti Avalanche is installed with a version lower than 6.4.3.602 and the web component is accessible 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.602 or later
Fixed in 6.4.3.602
Interim mitigation

Update Ivanti Avalanche to version 6.4.x or later to patch the unrestricted file upload vulnerability. Apply the update during a planned maintenance window following standard change management procedures.

Recommended fix High confidence

6.4.3.602 or later (6.4.x line)

  1. 1. Download Ivanti Avalanche version 6.4.3.602 or later from the official Ivanti portal.
  2. 2. Back up the current Avalanche configuration and database.
  3. 3. Stop the Ivanti Avalanche server services.
  4. 4. Install the upgraded Avalanche version (6.4.3.602 or later) following the standard upgrade procedure.
  5. 5. Verify the installation completed successfully.
  6. 6. Start the Avalanche server services.
  7. 7. Confirm the web component is accessible and functioning normally.

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

Fix this in Avalanche Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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