dbcve.org
AvalancheApplication · Ivanti

CVE-2023-38036

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-12
Fix available
A fix is available. Upgrade to 6.4.1 or later.
See remediation →
100/100
Remediation priority · Urgent
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 security vulnerability within Ivanti Avalanche Manager before version 6.4.1 may allow an unauthenticated attacker to create a buffer overflow that could result in service disruption or arbitrary 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 · high confidence

Ivanti Avalanche Manager before version 6.4.1 contains a buffer overflow vulnerability that can be exploited by an unauthenticated attacker, potentially allowing service disruption or arbitrary code execution. The vulnerability is pre-authentication and carries a CVSS score of 9.8, indicating critical severity.

MitigationUpgrade Ivanti Avalanche Manager to version 6.4.1 or later to remediate this vulnerability. Given the critical CVSS score and unauthenticated attack vector, prioritize this upgrade immediately.

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

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate Ivanti Avalanche Manager installation
    Check for Ivanti Avalanche Manager on the server or workstation. Common installation paths on Windows include C:\Program Files\Ivanti\Avalanche or C:\Program Files (x86)\Ivanti\Avalanche. On Linux, check /opt/ivanti/avalanche or /var/opt/avalanche.
    Affected if Ivanti Avalanche Manager is installed on the system
  2. Identify installed version via web console
    Log into the Ivanti Avalanche web console if accessible. Navigate to the About or System Information page, typically found under Help > About or System > Status. Record the displayed version number.
    Affected if The displayed version is less than 6.4.1 or cannot be determined (version unknown)
  3. Identify installed version via system utilities
    On Windows, open Programs and Features (appwiz.cpl) and locate 'Ivanti Avalanche Manager' in the list to view the installed version. On Linux, run the package manager command such as rpm -qi avalanche-manager or dpkg -l avalanche-manager.
    Affected if The version shown is less than 6.4.1
  4. Check service or daemon version
    If the web console is unavailable, check the Ivanti Avalanche service or daemon information. On Windows, view the properties of the 'Ivanti Avalanche Manager' service in Services (services.msc). On Linux, check the running process using ps aux | grep avalanche or query the init/systemd service.
    Affected if The service version or executable version is visible and is less than 6.4.1

The system is affected if Ivanti Avalanche Manager is present and the installed version is anything below 6.4.1.

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.1 or later
Fixed in 6.4.1
Interim mitigation

Upgrade Ivanti Avalanche Manager to version 6.4.1 or later to remediate this vulnerability. Given the critical CVSS score and unauthenticated attack vector, prioritize this upgrade immediately.

Recommended fix High confidence

6.4.1

  1. 1. Create a complete backup of the current Ivanti Avalanche installation, including configuration files and database
  2. 2. Download Ivanti Avalanche version 6.4.1 from the official Ivanti download portal (forums.ivanti.com or ivanti.com)
  3. 3. Stop the Avalanche Manager service before beginning the upgrade process
  4. 4. Run the installer for version 6.4.1, following the on-screen installation wizard prompts
  5. 5. Select the upgrade option when prompted to preserve existing configuration data
  6. 6. After installation completes, restart the Avalanche Manager service
  7. 7. Verify the upgrade by checking the Avalanche Manager version number in the administration console
  8. 8. Test critical Avalanche functionality to ensure the upgrade did not introduce regressions
Caveat Standard security upgrade; regression testing of core Avalanche features is recommended after applying this patch

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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