CVE-2022-36972
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 · uneditedThis 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-15328.
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 confidenceSQL injection vulnerability in the ProfileDaoImpl class of Ivanti Avalanche 6.3.2.3490 allows remote attackers to bypass authentication by crafting malicious SQL queries through user-supplied input that is directly incorporated into SQL statements without proper parameterization or sanitization.
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>= 6.3.2.3490, < 6.3.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Ivanti Avalanche versionCheck the installed version through the Avalanche management console (typically found in Help > About) or check the installer/registry for version 6.3.2.3490 through 6.3.3.xAffected if Installed version falls within >= 6.3.2.3490 and < 6.3.4
-
Locate the ProfileDaoImpl classInspect the application binaries or source code if available, looking for the ProfileDaoImpl class file in the Avalanche web application directoryAffected if The ProfileDaoImpl class exists in the deployment and handles user profile data
-
Determine if user-supplied input reaches SQL queriesReview application logs or intercept requests to the profile management functionality to observe if user input is passed directly to SQL statementsAffected if User input from profile fields is used in SQL queries without parameterized statements
-
Check network exposure of Avalanche management interfaceIdentify if port 8443 (default Avalanche console) or the web management interface is exposed to untrusted networksAffected if The management interface is reachable from networks without proper access controls
-
Verify authentication mechanismTest the login function with SQL injection payloads in username/password fields to observe if authentication can be bypassedAffected if The login accepts specially crafted input that alters SQL query logic (e.g., OR 1=1)
You are affected if Ivanti Avalanche version is between 6.3.2.3490 and 6.3.3.x and the management interface is accessible to untrusted users who could exploit the ProfileDaoImpl SQL injection to bypass authentication.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.3.4
Apply vendor patch when available; until then, restrict network access to the Avalanche management interface and implement WAF rules to detect and block SQL injection payloads.
Ivanti Avalanche 6.3.4 or later
- Download Ivanti Avalanche version 6.3.4 or later from the official Ivanti download portal (formerly download.wavelink.com)
- Review the upgrade documentation and release notes for version 6.3.4
- Create a backup of the current Avalanche installation and database
- Test the upgrade in a non-production environment first
- Apply the upgrade to the production environment following standard Ivanti upgrade procedures
- Verify the upgrade was successful and the SQL injection vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36972 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-36972 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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