dbcve.org
AvalancheApplication · Ivanti

CVE-2024-24993

HIGH · 7.5 CVSS v3.1 Published 2024-04-19
Fix available
A fix is available. Upgrade to 6.4.3.528 or later.
See remediation →
81/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 Race Condition (TOCTOU) 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 Time-of-Check-Time-of-Use (TOCTOU) race condition vulnerability exists in the web component of Ivanti Avalanche versions prior to 6.4.3. An authenticated remote attacker can exploit this timing window to execute arbitrary commands with SYSTEM-level privileges on the affected Windows host.

MitigationUpgrade Ivanti Avalanche to version 6.4.3 or later to remediate this vulnerability. If immediate patching is not possible, restrict network access to the Avalanche web interface to trusted personnel only.

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

CVSS:3.1/AV:N/AC:H/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 Windows Programs and Features or list installed applications for 'Ivanti Avalanche'. Alternatively, check for the Avalanche installation directory (commonly under C:\Program Files\ or C:\Program Files (x86)\).
    Affected if Ivanti Avalanche is present on the system.
  2. Identify installed Avalanche version
    Locate the Avalanche application or executable file and query its version property, or check the version information in the Windows installed programs list.
    Affected if The installed version is lower than 6.4.3.528.
  3. Verify the web component is accessible
    Check if the Avalanche web interface port (default 8080 or configured port) is listening and accessible from the network. Use 'netstat -an | findstr <port>' or check firewall rules.
    Affected if The web interface port is open and reachable from untrusted networks.
  4. Determine if untrusted authentication is possible
    Review the Avalanche web authentication configuration to confirm whether the login page is exposed to untrusted users rather than restricted to trusted IP addresses only.
    Affected if Untrusted or anonymous users can reach the login page.

A system is affected if Ivanti Avalanche with version below 6.4.3.528 is installed with its web component accessible to untrusted 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.528 or later
Fixed in 6.4.3.528
Interim mitigation

Upgrade Ivanti Avalanche to version 6.4.3 or later to remediate this vulnerability. If immediate patching is not possible, restrict network access to the Avalanche web interface to trusted personnel only.

Recommended fix Moderate confidence

Ivanti Avalanche 6.4.3.528 or later

  1. 1. Back up the current Ivanti Avalanche installation, including database and configuration files
  2. 2. Download Ivanti Avalanche version 6.4.3.528 or later from the official Ivanti support portal (forums.ivanti.com)
  3. 3. Stop the Avalanche services before applying the update
  4. 4. Follow the official Ivanti Avalanche upgrade documentation to install version 6.4.3.528 or later
  5. 5. After installation, restart Avalanche services
  6. 6. Verify the upgrade was successful by checking the Avalanche version in the administration console
  7. 7. Test critical Avalanche functionalities to ensure normal operation

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
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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