dbcve.org
AvalancheApplication · Ivanti

CVE-2022-36980

HIGH · 8.1 CVSS v3.1 Published 2023-03-29
Fix available
A fix is available. Upgrade to 6.3.4 or later.
See remediation →
90/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 bypass authentication 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 EnterpriseServer service. The issue results from the lack of proper locking when performing operations during authentication. An attacker can leverage this vulnerability to bypass authentication on the system. Was ZDI-CAN-15528.

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

Authentication bypass vulnerability in Ivanti Avalanche 6.3.2.3490's EnterpriseServer service. The flaw results from lack of proper locking during authentication operations, allowing remote attackers to bypass the existing authentication mechanism.

MitigationApply vendor-provided patch for Ivanti Avalanche to address the authentication bypass in the EnterpriseServer service; verify authentication controls function correctly after patching.

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

CVSS:3.1/AV:N/AC:H/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. Identify Ivanti Avalanche installation
    Look for Ivanti Avalanche installation directory (commonly C:\Program Files\Ivanti\Avalanche or C:\Program Files (x86)\Ivanti\Avalanche on Windows, or /opt/avalanche on Linux). Also check for the EnterpriseServer service using 'sc query' on Windows or 'systemctl list-units' on Linux.
    Affected if Ivanti Avalanche software is present on the system
  2. Determine installed version
    Check the version of the EnterpriseServer component. On Windows, inspect the file properties of EnterpriseServer.exe in the installation bin folder, or check the registry key HKLM\SOFTWARE\Ivanti\Avalanche\Version. On Linux, check /opt/avalanche/bin/EnterpriseServer --version or the version file in the installation directory.
    Affected if The installed version falls within the range >= 6.3.2.3490 and < 6.3.4
  3. Verify EnterpriseServer service status
    Confirm the EnterpriseServer service is running and enabled. On Windows use 'sc query EnterpriseServer' or check Services.msc. On Linux use 'systemctl status avalanche-enterprise-server' or check process list for EnterpriseServer process.
    Affected if The EnterpriseServer service is actively running
  4. Assess network exposure
    Check if the EnterpriseServer port (default TCP 443 or 80) is listening on interfaces accessible from untrusted networks. Review firewall rules and network configuration. Use 'netstat -an | grep -E "(443|80)"' or check IIS/web server bindings if applicable.
    Affected if EnterpriseServer is reachable from untrusted network segments

You are affected if Ivanti Avalanche with EnterpriseServer is installed with a version between 6.3.2.3490 and 6.3.3.x (anything < 6.3.4) and the service is network-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-provided patch for Ivanti Avalanche to address the authentication bypass in the EnterpriseServer service; verify authentication controls function correctly after patching.

Recommended fix Moderate confidence

Ivanti Avalanche 6.3.4 or later

  1. Download Ivanti Avalanche version 6.3.4 or later from the official vendor source (download.wavelink.com or Ivanti support portal)
  2. Review the upgrade documentation and release notes for Ivanti Avalanche
  3. Ensure you have a verified backup of the current Avalanche configuration
  4. Stop the Avalanche EnterpriseServer service before upgrading
  5. Install version 6.3.4 or latest stable release
  6. Verify the EnterpriseServer service starts successfully
  7. Confirm the authentication mechanism now properly implements locking during authentication operations
  8. Test that authentication flows work correctly for valid users
Caveat Review release notes for any configuration or feature changes between 6.3.2.3490 and 6.3.4

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
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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