dbcve.org
AvalancheApplication · Ivanti

CVE-2024-50318

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
A null pointer dereference 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 · high confidence

A null pointer dereference vulnerability in Ivanti Avalanche versions prior to 6.4.6 allows a remote unauthenticated attacker to crash the application service by triggering the dereference of a null pointer, 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. Locate the Ivanti Avalanche installation
    Identify where Ivanti Avalanche is installed on the system. This is typically found in the program files directory or can be located by searching for 'Avalanche' in Windows Programs and Features.
    Affected if The application is installed on the system.
  2. Determine the installed version of Ivanti Avalanche
    Check the version of Ivanti Avalanche using one of the following methods: (1) Right-click the Avalanche application in Programs and Features and select 'Properties' to view the Version, (2) Right-click the main Avalanche executable (e.g., Avalanche.exe) and select 'Properties' > 'Details' to view the File Version, or (3) Access the application's Help > About menu if the GUI is accessible.
    Affected if The application is installed.
  3. Compare the installed version against the affected range
    Compare the version number found in the previous step to the fixed version 6.4.6. Ensure you capture the full version string (e.g., 6.4.0, 6.4.3, 6.4.5).
    Affected if The installed version is lower than 6.4.6 (for example, 6.4.0 through 6.4.5).
  4. Identify if the Avalanche service is running and accessible
    Verify that the Ivanti Avalanche service or server component is currently running and reachable on the network. This can be done by checking the Windows Services console or attempting to access the Avalanche web interface or administrative port if applicable.
    Affected if The service is running and accessible to network users.

If the installed version of Ivanti Avalanche is lower than 6.4.6 and the service is accessible, the environment is affected by this vulnerability and could be crashed by a remote unauthenticated attacker.

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. Obtain the Ivanti Avalanche 6.4.6 upgrade package from the official Ivanti download portal or through your licensed support channel
  2. Review the Ivanti Avalanche upgrade documentation for pre-upgrade requirements and procedures
  3. Ensure you have a complete backup of the current Avalanche installation and database
  4. Stop the Ivanti Avalanche services before beginning the upgrade
  5. Run the upgrade installer for version 6.4.6 following the documented installation steps
  6. After installation, verify all Avalanche services start correctly
  7. Confirm the upgrade was successful by checking the Avalanche version in the administration console

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

Fix this in Avalanche Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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