dbcve.org
AvalancheApplication · Ivanti

CVE-2022-36975

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 ProfileDaoImpl 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-15332.

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

A SQL injection vulnerability in the ProfileDaoImpl class of Ivanti Avalanche 6.3.2.3490 allows remote attackers to bypass authentication by crafting malicious requests that execute arbitrary SQL queries constructed from user-supplied input without proper sanitization.

MitigationApply the vendor patch or upgrade to a patched version of Ivanti Avalanche. If immediate patching is not possible, restrict network access to the Avalanche administration interface to minimize exposure.

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. Identify if Ivanti Avalanche is installed
    Review your environment for Ivanti Avalanche software components, typically found in program files or the application server directory where Avalanche was deployed.
    Affected if The software is present on the system
  2. Determine the installed version of Ivanti Avalanche
    Access the Avalanche administration interface or check the software inventory/system registry for the exact version number of the installed Ivanti Avalanche instance.
    Affected if The installed version is 6.3.2.3490 or higher but lower than 6.3.4
  3. Locate the ProfileDaoImpl class
    Inspect the Avalanche application binaries or source code if available, looking for the ProfileDaoImpl class file within the deployed application packages.
    Affected if The ProfileDaoImpl class exists in the application and is in use
  4. Assess network exposure of the Avalanche administration interface
    Determine if the Avalanche administration web interface is accessible from untrusted networks by reviewing firewall rules, network segmentation, and access control lists.
    Affected if The administration interface is reachable from external or untrusted networks

A user is affected if Ivanti Avalanche version 6.3.2.3490 through 6.3.3.x is installed and the administration interface is network-accessible, since the ProfileDaoImpl class SQL injection can be exploited remotely to bypass authentication.

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 patched version of Ivanti Avalanche. If immediate patching is not possible, restrict network access to the Avalanche administration interface to minimize exposure.

Recommended fix Moderate confidence

6.3.4 or later

  1. Identify the current installed version of Ivanti Avalanche by accessing the administration console or checking system information
  2. Confirm the version is >= 6.3.2.3490 and < 6.3.4 to confirm vulnerability status
  3. Download Ivanti Avalanche version 6.3.4 or later from the official vendor download portal (download.wavelink.com)
  4. Follow vendor documentation for upgrading Ivanti Avalanche, ensuring proper backup of configuration and database before proceeding
  5. Apply the upgrade in a test environment first to validate functionality
  6. After successful testing, apply the upgrade to production environments
  7. Verify the upgrade was successful by confirming the new version number in the administration console
Caveat Review Ivanti Avalanche release notes for any compatibility changes or deprecated features between current and target version before upgrading

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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