dbcve.org
AvalancheApplication · Ivanti

CVE-2025-8297

HIGH · 7.2 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 6.4.8.8008 or later.
See remediation →
78/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
Incomplete restriction of configuration in Ivanti Avalanche before version 6.4.8.8008 allows a remote authenticated attacker with admin privileges to achieve remote code execution

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 before version 6.4.8.8008 contains an incomplete restriction of configuration that allows an authenticated administrator to achieve remote code execution. The vulnerability stems from insufficient access controls on configuration settings that can be abused to execute arbitrary commands on the underlying system.

MitigationUpgrade Ivanti Avalanche to version 6.4.8.8008 or later. Restrict administrative access to trusted personnel and monitor for unauthorized configuration changes.

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

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. Identify the installed Ivanti Avalanche version
    Locate the version information for Ivanti Avalanche in the product's web interface under System or About, or check the installer/registry entries if locally accessible. Compare the version number to 6.4.8.8008.
    Affected if The installed version is lower than 6.4.8.8008 (for example, 6.4.7.x, 6.4.6.x, or earlier).
  2. Confirm administrative access exists
    Review the list of user accounts with administrator-level privileges in Ivanti Avalanche. Determine whether there are active administrator accounts or if external authentication (such as LDAP) is configured.
    Affected if There is at least one authenticated administrator account that can log into the Avalanche administration console.
  3. Review configuration settings for command execution options
    Inspect the system configuration, scheduled task settings, or custom script/execution paths within the Avalanche administration console. Look for fields that accept file paths, commands, or script content that may be executed by the system.
    Affected if Configuration options exist that allow specification of arbitrary commands or scripts to be run on the underlying operating system.

You are affected if Ivanti Avalanche is installed at a version lower than 6.4.8.8008 AND an authenticated administrator can access configuration settings that allow command execution.

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.8.8008 or later
Fixed in 6.4.8.8008
Interim mitigation

Upgrade Ivanti Avalanche to version 6.4.8.8008 or later. Restrict administrative access to trusted personnel and monitor for unauthorized configuration changes.

Recommended fix Moderate confidence

Ivanti Avalanche version 6.4.8.8008 or later

  1. 1. Verify current Ivanti Avalanche version by checking the About or System Information section in the admin console
  2. 2. Download Ivanti Avalanche version 6.4.8.8008 or later from the official Ivanti download portal or contact Ivanti Customer Support
  3. 3. Review Ivanti upgrade documentation and release notes for version 6.4.8.8008
  4. 4. Create a complete backup of the current Avalanche installation including database and configuration files
  5. 5. Stop the Avalanche server services before upgrading
  6. 6. Install version 6.4.8.8008 following the official upgrade procedure
  7. 7. Verify the upgrade was successful by checking the version in the admin console
  8. 8. Test critical Avalanche functionality to ensure normal operations

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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