dbcve.org
AvalancheApplication · Ivanti

CVE-2021-42132

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
High EPSS 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
A command Injection vulnerability exists in Ivanti Avalanche before 6.3.3 allows an attacker with access to the Inforail Service to perform arbitrary command execution.

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

A command injection vulnerability in the Inforail Service component of Ivanti Avalanche versions prior to 6.3.3 allows an attacker with access to the service to execute arbitrary operating system commands. The vulnerability stems from insufficient input validation allowing malicious commands to be passed through to the underlying system.

MitigationUpgrade Ivanti Avalanche to version 6.3.3 or later. If immediate patching is not possible, restrict network access to the Inforail Service and implement additional authentication controls.

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 Ivanti Avalanche installation on the system - look for the application in installed programs (Windows) or package lists (Linux), or check common installation directories.
    Affected if Ivanti Avalanche is present on the system
  2. Determine installed version of Ivanti Avalanche
    Locate the version information for the Avalanche installation - check the application itself, registry entries (Windows), configuration files, or use any available version query commands.
    Affected if The installed version is any version prior to 6.3.3 (e.g., 6.3.2, 6.3.1, 6.3.0, etc.)
  3. Check if Inforail Service is running
    Identify whether the Inforail Service component is active on the system - this may appear as a running service, process, or be documented in the application's service/configuration documentation.
    Affected if The Inforail Service is enabled and running on the system
  4. Assess network exposure of Inforail Service
    Determine if the Inforail Service is accessible over the network - check firewall rules, port bindings, and network configuration to see if the service is exposed to network access.
    Affected if The Inforail Service is network-accessible beyond the localhost or trusted internal networks

The environment is affected if Ivanti Avalanche is installed with a version prior to 6.3.3 and the Inforail Service component is running and 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.3 or later
Fixed in 6.3.3
Interim mitigation

Upgrade Ivanti Avalanche to version 6.3.3 or later. If immediate patching is not possible, restrict network access to the Inforail Service and implement additional authentication controls.

Recommended fix Moderate confidence

Avalanche 6.3.3

  1. 1. Back up the current Ivanti Avalanche installation and database before proceeding with the upgrade.
  2. 2. Download Ivanti Avalanche version 6.3.3 or later from the official Ivanti download portal.
  3. 3. Stop the Avalanche services, including the Inforail Service.
  4. 4. Install the updated Avalanche 6.3.3 package following the standard upgrade procedure.
  5. 5. Verify that the Inforail Service is running correctly after the upgrade.
  6. 6. Test that the command injection vulnerability is no longer present and that normal Avalanche functionality works as expected.

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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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