dbcve.org
AvalancheApplication · Ivanti

CVE-2022-43555

HIGH · 7.8 CVSS v3.1 Published 2023-11-03
Fix available
A fix is available. Upgrade to 6.4.1.236 or later.
See remediation →
80/100
Remediation priority · High
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
Ivanti Avalanche Printer Device Service Missing Authentication Local Privilege Escalation Vulnerability

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 · moderate confidence

Ivanti Avalanche Printer Device Service lacks proper authentication controls, allowing a local unprivileged attacker to escalate privileges to higher levels (likely SYSTEM) by interacting with the vulnerable service.

MitigationApply the vendor security patch for CVE-2022-43555 to Ivanti Avalanche, or if the Printer Device Service is not required, disable it as a compensating control.

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

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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. Verify Ivanti Avalanche is installed
    Check for Ivanti Avalanche installation directories (commonly under Program Files or Program Files (x86)) or look for the 'Avalanche' service in Windows Services. Use: Get-Service | Where-Object {$_.DisplayName -like '*Avalanche*'}
    Affected if The software is installed and the Printer Device Service exists
  2. Determine installed Ivanti Avalanche version
    Check the version of the Avalanche installation - typically found in the main executable (e.g., avalanche.exe) or in the software's About/Version information. Compare the version number to 6.4.1.236
    Affected if Installed version is lower than 6.4.1.236
  3. Identify Printer Device Service status
    Locate and check the Printer Device Service (service name typically contains 'Avalanche' and 'Printer' or 'Device'). Use: Get-Service | Where-Object {$_.DisplayName -like '*Avalanche*Printer*' -or $_.Name -like '*Avalanche*Printer*'} to see if it exists and its current state
    Affected if The Printer Device Service exists and is running
  4. Check service execution context
    Use 'sc qc' or Get-WmiObject Win32_Service to examine the service configuration, specifically the 'StartName' (BinaryPathName) to see what account the service runs under
    Affected if Service runs under a high-privilege account (e.g., SYSTEM, LocalSystem) and is accessible to unprivileged local users

User is affected if Ivanti Avalanche is installed with version lower than 6.4.1.236 and the Printer Device Service is running on the system.

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.4.1.236 or later
Fixed in 6.4.1.236
Interim mitigation

Apply the vendor security patch for CVE-2022-43555 to Ivanti Avalanche, or if the Printer Device Service is not required, disable it as a compensating control.

Recommended fix High confidence

6.4.1.236 or later

  1. 1. Back up the current Ivanti Avalanche configuration and database
  2. 2. Download Ivanti Avalanche version 6.4.1.236 or later from the official vendor download portal (download.wavelink.com or official Ivanti channels)
  3. 3. Stop the Avalanche services before performing the upgrade
  4. 4. Install or upgrade to Avalanche version 6.4.1.236 or later
  5. 5. Restart the Avalanche services
  6. 6. Verify the Printer Device Service is running and accessible
  7. 7. Confirm the upgrade was successful by checking the installed version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Avalanche Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
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,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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