dbcve.org
AvalancheApplication · Ivanti

CVE-2022-36973

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 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 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-15329.

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

SQL injection vulnerability in the ProfileDaoImpl class of Ivanti Avalanche allows remote attackers to bypass authentication by crafting malicious SQL queries through user-supplied input. Despite the description indicating authentication is required, the SQL injection enables attackers to circumvent the authentication mechanism entirely.

MitigationApply vendor security patch for CVE-2022-36973 when available; until then, restrict network access to Ivanti Avalanche management interfaces and implement WAF rules to detect SQL injection attempts.

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. Confirm Ivanti Avalanche installation
    Identify if Ivanti Avalanche is installed on the system by checking for the Avalanche application directory, service, or running process
    Affected if Ivanti Avalanche software is present on the system
  2. Check installed version
    Locate the Ivanti Avalanche version information, typically found in the application properties, about dialog, or version file within the Avalanche installation directory
    Affected if The installed version is 6.3.2.3490 or higher but lower than 6.3.4
  3. Identify exposed management interface
    Check network configuration to determine if the Ivanti Avalanche management console (typically ports 80/443 or configured HTTP/HTTPS ports) is accessible from untrusted networks
    Affected if The management interface is accessible from network segments that include untrusted or external hosts
  4. Locate ProfileDaoImpl class file
    Search for the ProfileDaoImpl class file within the Avalanche application directories, typically found in WEB-INF/classes or similar application library paths
    Affected if The ProfileDaoImpl class file exists in the application, indicating the vulnerable component is present
  5. Review authentication logs for anomalies
    Examine Ivanti Avalanche server logs, especially authentication and database query logs, for unusual SQL syntax or authentication patterns that may indicate exploitation attempts
    Affected if Log entries show SQL injection patterns in authentication parameters or unexpected authentication bypasses

The environment is affected if Ivanti Avalanche version 6.3.2.3490 through 6.3.3.x is installed and its management interface 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 security patch for CVE-2022-36973 when available; until then, restrict network access to Ivanti Avalanche management interfaces and implement WAF rules to detect SQL injection attempts.

Recommended fix High confidence

Ivanti Avalanche 6.3.4

  1. Obtain Ivanti Avalanche version 6.3.4 from the official Ivanti download portal or your licensed distribution channel
  2. Back up the current Avalanche configuration and database before proceeding with the upgrade
  3. Upgrade the Ivanti Avalanche installation to version 6.3.4 using the standard upgrade procedure
  4. After upgrade, verify that the ProfileDaoImpl class has been updated and test that authentication functions correctly
  5. Confirm the SQL injection vulnerability is no longer present by reviewing system logs for any previously exploited SQL injection attempts

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 / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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