dbcve.org
AvalancheApplication · Ivanti

CVE-2024-50319

HIGH · 7.5 CVSS v3.1 Published 2024-11-12
Fix available
A fix is available. Upgrade to 6.4.6 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 infinite loop in Ivanti Avalanche before 6.4.6 allows a remote unauthenticated attacker to cause a 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 · moderate confidence

Ivanti Avalanche versions before 6.4.6 contain an infinite loop vulnerability that can be triggered by a remote unauthenticated attacker, resulting in denial of service.

MitigationUpgrade Ivanti Avalanche to version 6.4.6 or later to remediate this vulnerability.

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

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 your systems for the presence of Ivanti Avalanche software. This may be found in installed programs list, application directories, or running services on Windows or Linux systems where the product was deployed.
    Affected if Ivanti Avalanche software is present on the system
  2. Identify the installed version of Ivanti Avalanche
    Locate the version information for Ivanti Avalanche. This is typically accessible through the product's web interface under Help or About sections, or via command-line tools if available in your installation. Check product documentation for version lookup specific to your deployment.
    Affected if The version returned is lower than 6.4.6
  3. Compare the installed version against the affected range
    Take the identified version number and compare it to the affected range: any version before 6.4.6 is vulnerable. Ensure you capture the full version string including any patch levels.
    Affected if The installed version is 6.4.5 or earlier, or any pre-6.4.6 release
  4. Confirm network exposure of the Avalanche service
    Since this vulnerability can be triggered by a remote unauthenticated attacker, determine if the Ivanti Avalanche web interface or service ports are accessible from network locations. Check firewall rules, listening ports, and access controls.
    Affected if The Avalanche service is reachable from untrusted networks without authentication

You are affected if Ivanti Avalanche is installed with a version lower than 6.4.6 and the service is network-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.6 or later
Fixed in 6.4.6
Interim mitigation

Upgrade Ivanti Avalanche to version 6.4.6 or later to remediate this vulnerability.

Recommended fix Moderate confidence

6.4.6

  1. 1. Back up the current Ivanti Avalanche installation and database before proceeding with the upgrade.
  2. 2. Download Ivanti Avalanche version 6.4.6 from the official Ivanti download portal or support site.
  3. 3. Review Ivanti's official upgrade documentation for Avalanche 6.4.x to ensure prerequisites are met.
  4. 4. Stop the Avalanche server services to prepare for the upgrade process.
  5. 5. Install Avalanche 6.4.6 following the standard upgrade procedure documented by Ivanti.
  6. 6. Start the Avalanche services and verify the application is running correctly.
  7. 7. Test that the Avalanche console is accessible and all expected functionality is working.

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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