dbcve.org
AvalancheApplication · Ivanti

CVE-2022-36971

HIGH · 8.8 CVSS v3.1 Published 2023-03-29
Fix available
A fix is available. Upgrade to 6.3.4 or later.
See remediation →
94/100
Remediation priority · Urgent
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
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 JwtTokenUtility class. 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-15301.

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 the JwtTokenUtility class of Ivanti Avalanche. While exploitation requires authentication, the authentication mechanism can be bypassed, allowing remote attackers to deserialize untrusted data and execute arbitrary code in the context of the service account.

MitigationApply vendor-supplied patches for Ivanti Avalanche to address the deserialization flaw in JwtTokenUtility and the authentication bypass. If patches are unavailable, consider network segmentation to limit exposure to trusted users 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.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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. Identify Ivanti Avalanche installation
    Locate the Ivanti Avalanche installation directory and check for version information files, typically found in the installation root folder or within a version/info file
    Affected if The installed version falls within >= 6.3.2.3490 and < 6.3.4
  2. Check Windows installed programs
    Open Windows Control Panel > Programs and Features or run 'appwiz.cpl' to view installed software and locate Ivanti Avalanche with its version number
    Affected if The displayed version is between 6.3.2.3490 and 6.3.3.x (any version less than 6.3.4)
  3. Verify JwtTokenUtility component presence
    Examine the Ivanti Avalanche web application files for the JwtTokenUtility class file, typically located in the web application's bin or application directories
    Affected if The JwtTokenUtility class file exists in the deployed web application
  4. Confirm web service accessibility
    Check if the Avalanche web console or associated web services are exposed externally or accessible over the network by reviewing IIS/website bindings or firewall rules
    Affected if The web interface is accessible from untrusted networks without proper network restrictions
  5. Review authentication configuration
    Inspect the authentication configuration settings within the Avalanche administration console or configuration files to determine if default authentication is enabled
    Affected if Default authentication settings are in use and the authentication bypass condition exists

A system is affected if Ivanti Avalanche version is 6.3.2.3490 or higher but lower than 6.3.4, and the web service component is accessible.

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 vendor-supplied patches for Ivanti Avalanche to address the deserialization flaw in JwtTokenUtility and the authentication bypass. If patches are unavailable, consider network segmentation to limit exposure to trusted users only.

Recommended fix High confidence

Ivanti Avalanche 6.3.4 or later

  1. 1. Identify the current Ivanti Avalanche version by accessing the administration console or checking the system information.
  2. 2. Confirm the version is >= 6.3.2.3490 and < 6.3.4, which confirms vulnerability to CVE-2022-36971.
  3. 3. Prior to upgrade, perform a complete backup of the Avalanche database and configuration.
  4. 4. Download Ivanti Avalanche version 6.3.4 or later from the official vendor source (download.wavelink.com or Ivanti support portal).
  5. 5. Apply the upgrade following Ivanti's standard upgrade procedure for Avalanche.
  6. 6. After upgrade, verify the new version is 6.3.4 or higher.
  7. 7. Validate that the JwtTokenUtility class has been patched and the service is functioning normally.
Caveat Review Ivanti Avalanche 6.3.4 release notes for any compatibility or configuration changes before upgrading

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

Fix this in Avalanche Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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