dbcve.org
AvalancheApplication · Ivanti

CVE-2021-42126

HIGH · 8.8 CVSS v3.1 Published 2021-12-07
Fix available
A fix is available. Upgrade to 6.3.3 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
An improper authorization control vulnerability exists in Ivanti Avalanche before 6.3.3 allows an attacker with access to the Inforail Service to perform privilege escalation.

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 before version 6.3.3 contains an improper authorization control vulnerability in the Inforail Service component. An attacker who already has access to the Inforail Service can exploit this authorization flaw to escalate privileges, potentially gaining administrative or higher-level access within the application.

MitigationUpgrade Ivanti Avalanche to version 6.3.3 or later to remediate the improper authorization vulnerability in the Inforail Service.

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

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. Verify Ivanti Avalanche is installed
    Check for Avalanche installation directory (commonly at C:\Program Files\Ivanti\Avalanche or /opt/ avalanche) or look for the Avalanche service in Windows Services or Linux service list
    Affected if Ivanti Avalanche is found installed on the system
  2. Determine installed Avalanche version
    Check the version of Ivanti Avalanche by inspecting the executable or DLL properties (often AvalancheServer.exe or similar in the installation bin folder), or use the application's about/help section
    Affected if Installed version is lower than 6.3.3 (e.g., 6.3.2, 6.3.1, 6.3.0, 6.2.x, etc.)
  3. Confirm Inforail Service is running
    Check if the Inforail Service (inforail.exe or Inforail service) is running on the system via Windows Services, Task Manager, or Linux process list
    Affected if Inforail Service is running and exposed to the network or accessible to untrusted users
  4. Verify Inforail Service authorization controls
    Inspect the Inforail Service configuration files or web service settings to determine if proper authorization is enforced on the Inforail endpoints
    Affected if Inforail Service lacks proper authorization controls or allows unauthenticated/lower-privilege access to privileged operations

User is affected if Ivanti Avalanche version is below 6.3.3 AND the Inforail Service is running and accessible without proper authorization controls in place.

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.3 or later
Fixed in 6.3.3
Interim mitigation

Upgrade Ivanti Avalanche to version 6.3.3 or later to remediate the improper authorization vulnerability in the Inforail Service.

Recommended fix High confidence

Ivanti Avalanche 6.3.3

  1. Back up the current Ivanti Avalanche configuration and database before starting the upgrade process
  2. Download Ivanti Avalanche version 6.3.3 or later from the official Ivanti download portal or through your licensed support channel
  3. Stop all Avalanche services including the Inforail Service
  4. Install the Avalanche 6.3.3 upgrade following the official Ivanti upgrade documentation
  5. After installation, verify that all services start successfully
  6. Confirm the Inforail Service is running with the updated authorization controls
Caveat No breaking changes documented in the provided information

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

Fix this in Avalanche Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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