dbcve.org
AvalancheApplication · Ivanti

CVE-2022-36974

CRITICAL · 9.8 CVSS v3.1 Published 2023-03-29
Fix available
A fix is available. Upgrade to 6.3.4 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS 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
This vulnerability allows remote attackers to execute arbitrary code on affected installations of Ivanti Avalanche 6.3.2.3490. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed. The specific flaw exists within the Web File Server service. The issue results from the lack of proper validation of user-supplied data, which can result in deserialization of untrusted data. An attacker can leverage this vulnerability to execute code in the context of the service account. Was ZDI-CAN-15330.

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

This is a deserialization vulnerability in Ivanti Avalanche's Web File Server service. Attackers can bypass the authentication mechanism and then exploit improper validation of user-supplied data to deserialize untrusted data, achieving remote code execution as the service account.

MitigationApply the vendor patch or upgrade to a fixed version of Ivanti Avalanche that addresses this deserialization vulnerability and the authentication bypass.

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.3.2.3490, < 6.3.4

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. Confirm Ivanti Avalanche is installed
    Inspect the system for Ivanti Avalanche installation files or check installed programs list
    Affected if Ivanti Avalanche software is present on the system
  2. Locate the installed version of Ivanti Avalanche
    Find the version information for the Ivanti Avalanche installation, typically available in program details or about section
    Affected if Version cannot be determined or is not visible
  3. Compare installed version to vulnerable range
    Check if the installed version falls within >= 6.3.2.3490 and < 6.3.4
    Affected if Installed version is 6.3.2.3490 or higher but lower than 6.3.4
  4. Verify Web File Server service status
    Check if the Web File Server component of Ivanti Avalanche is running, as this is the vulnerable component
    Affected if Web File Server service is active and version is in the vulnerable range

The environment is affected if Ivanti Avalanche is installed with a version >= 6.3.2.3490 and < 6.3.4 and the Web File Server service is enabled.

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.3.4 or later
Fixed in 6.3.4
Interim mitigation

Apply the vendor patch or upgrade to a fixed version of Ivanti Avalanche that addresses this deserialization vulnerability and the authentication bypass.

Recommended fix Moderate confidence

Ivanti Avalanche 6.3.4 or later

  1. Identify the current installed version of Ivanti Avalanche by accessing the administration interface or checking system information
  2. Download Ivanti Avalanche version 6.3.4 or later from the official vendor download portal (download.wavelink.com or via Ivanti support)
  3. Review Ivanti Avalanche upgrade documentation for your specific deployment type
  4. Create a complete backup of the current Avalanche configuration and database
  5. Test the upgrade in a non-production environment first
  6. Apply the upgrade during a planned maintenance window following Ivanti's standard upgrade procedures
  7. Verify the upgrade was successful by checking the version number and confirming all services are running properly
Caveat Review Ivanti release notes for 6.3.4 to check for any configuration or feature changes that may require adjustment

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

Fix this in Avalanche Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,540
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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