dbcve.org
AvalancheApplication · Ivanti

CVE-2022-36983

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. Authentication is not required to exploit this vulnerability. The specific flaw exists within the SetSettings class. The issue results from the lack of authentication prior to allowing access to functionality. An attacker can leverage this vulnerability to bypass authentication on the system. Was ZDI-CAN-15919.

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 critical authentication bypass vulnerability in Ivanti Avalanche's SetSettings class. The vulnerability allows remote unauthenticated attackers to bypass authentication mechanisms and access sensitive system functionality. The flaw exists because the SetSettings class does not verify authentication before allowing access to privileged operations.

MitigationApply the vendor-provided patch for CVE-2022-36983 immediately. If a patch is unavailable, implement authentication verification in the SetSettings class and restrict network access to the Avalanche service from untrusted sources until the fix is available.

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.3.101, < 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
    Locate the Ivanti Avalanche installation directory or check for the Avalanche service running on the system. Common paths include C:\Program Files\Ivanti\Avalanche or /opt/avalanche. Use 'services.msc' on Windows or check running processes for 'Avalanche' or 'avalanche' to verify the application is present.
    Affected if Ivanti Avalanche software is not found on the system, the user is not affected.
  2. Determine installed Avalanche version
    Check the installed version by reviewing the Avalanche application files, service properties, or version information typically found in the program's About section or in version metadata files within the installation directory. Compare the version number to the affected range: 6.3.3.101 through 6.3.3.x.
    Affected if The installed version falls within >= 6.3.3.101 and < 6.3.4, indicating the system is running a vulnerable version.
  3. Identify the SetSettings class endpoint
    Review Avalanche configuration files or web service definitions to locate the SetSettings class endpoint. This is typically exposed through the Avalanche web interface or API. Check for .NET assemblies, web.config files, or service definition files that reference 'SetSettings' functionality.
    Affected if The SetSettings class endpoint is present and accessible within the Avalanche installation, which is required for the vulnerability to be exploitable.
  4. Verify SetSettings does not enforce authentication
    Attempt to access the SetSettings functionality without providing credentials or a valid session token. If the application allows unauthenticated access to SetSettings operations, the vulnerability is present. Review application logs for denied authentication failures when accessing this endpoint.
    Affected if The SetSettings endpoint responds to requests without requiring authentication, confirming the authentication bypass flaw exists.

A user is affected if Ivanti Avalanche is installed with version 6.3.3.101 through 6.3.3.x and the SetSettings class endpoint is accessible without 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-provided patch for CVE-2022-36983 immediately. If a patch is unavailable, implement authentication verification in the SetSettings class and restrict network access to the Avalanche service from untrusted sources until the fix is available.

Recommended fix High confidence

Ivanti Avalanche 6.3.4 or later

  1. 1. Identify the current Ivanti Avalanche version by checking the application or system information
  2. 2. Create a complete backup of the Avalanche database and configuration files
  3. 3. Download Ivanti Avalanche version 6.3.4 or later from the official vendor download portal (download.wavelink.com)
  4. 4. Review the upgrade documentation and ensure system requirements are met
  5. 5. Stop the Avalanche service before applying the upgrade
  6. 6. Apply the upgrade following the vendor's standard upgrade procedure
  7. 7. Start the Avalanche service after upgrade completion
  8. 8. Verify the upgrade was successful by checking the version number
Caveat Standard upgrade considerations apply - review release notes for any configuration or feature changes between your current version 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
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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 locally
dbcve dependency scanner

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