dbcve.org
AvalancheApplication · Ivanti

CVE-2022-36976

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
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. The specific flaw exists within the GroupDaoImpl class. A crafted request can trigger execution of SQL queries composed from a user-supplied string. An attacker can leverage this vulnerability to bypass authentication on the system. Was ZDI-CAN-15333.

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 SQL injection vulnerability in the GroupDaoImpl class of Ivanti Avalanche that allows remote attackers to bypass authentication. The flaw allows execution of attacker-controlled SQL queries composed from user-supplied strings, enabling authentication bypass on affected installations.

MitigationApply the vendor security patch or update to a non-vulnerable version of Ivanti Avalanche. As a compensating control, deploy or update WAF rules to detect and block SQL injection attempts until patching is complete.

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
    Check if the Ivanti Avalanche application is present on the system by reviewing installed programs, services, or the application directory.
    Affected if Ivanti Avalanche software is found on the system
  2. Identify the installed version
    Locate the version information for Ivanti Avalanche, typically found in the application itself, an about page, or installation metadata.
    Affected if The version cannot be determined or is not immediately visible
  3. Compare version against affected range
    Determine if the installed version falls within >= 6.3.2.3490 and < 6.3.4.
    Affected if The installed version is 6.3.2.3490 or higher but lower than 6.3.4
  4. Verify application accessibility
    Confirm the Ivanti Avalanche web interface or remote access service is exposed and reachable.
    Affected if The application is accessible remotely and the vulnerable version condition is met

The environment is affected if Ivanti Avalanche is installed and running a version between 6.3.2.3490 and 6.3.3 inclusive.

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 security patch or update to a non-vulnerable version of Ivanti Avalanche. As a compensating control, deploy or update WAF rules to detect and block SQL injection attempts until patching is complete.

Recommended fix High confidence

Ivanti Avalanche 6.3.4 or later

  1. 1. Verify current Ivanti Avalanche version by accessing the admin console or checking the installed software
  2. 2. Download Ivanti Avalanche version 6.3.4 or later from the official Ivanti download portal (download.wavelink.com or Ivanti support site)
  3. 3. Review Ivanti Avalanche upgrade documentation and release notes for version 6.3.4
  4. 4. Create a complete backup of the current Avalanche installation, including database and configuration files
  5. 5. Schedule a maintenance window as the upgrade may require service restart
  6. 6. Stop the Avalanche services before upgrading
  7. 7. Install Avalanche version 6.3.4 or later following the official installation/upgrade procedures
  8. 8. Start Avalanche services after installation completes
Caveat Standard upgrade considerations apply - ensure compatibility with existing integrations and review release notes for any configuration changes

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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