dbcve.org
AvalancheApplication · Ivanti

CVE-2021-42131

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 SQL Injection vulnerability exists in Ivanti Avalance 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

SQL Injection vulnerability in the Inforail Service component of Ivanti Avalance versions prior to 6.3.3 allows an attacker with existing access to the Inforail Service to inject malicious SQL queries, potentially escalating privileges to higher-tier accounts or administrative roles.

MitigationUpgrade Ivanti Avalance to version 6.3.3 or later to receive the vendor patch for this SQL injection vulnerability. If immediate upgrade is not feasible, restrict network access to the Inforail Service and monitor for suspicious SQL patterns in service logs.

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. Identify installed Ivanti Avalanche version
    Check the application's About page, installation directory, or registry for the exact version number of Ivanti Avalanche
    Affected if The installed version is any version prior to 6.3.3 (e.g., 6.3.2, 6.3.1, 6.3.0, or earlier)
  2. Confirm Inforail Service presence
    Locate the Inforail Service component in the Ivanti Avalanche installation - check Windows Services list or process list for Inforail service process
    Affected if The Inforail Service is installed and running on the system
  3. Verify Inforail Service network accessibility
    Review firewall rules, network bindings, or service configuration to determine if Inforail Service listens on network interfaces or is restricted to localhost only
    Affected if Inforail Service is bound to a network-adjacent IP or port and is accessible from systems other than the local host
  4. Review Inforail Service logs for SQL anomalies
    Examine Inforail Service log files for unusual SQL syntax, unexpected database queries, or SQL error messages that may indicate injection attempts
    Affected if Logs contain SQL syntax errors, abnormally long queries, or patterns suggesting injection activity
  5. Audit Inforail Service account privileges
    Check the service account credentials used by Inforail Service and review database permissions assigned to that account
    Affected if The Inforail Service account has elevated database permissions (such as db_owner, admin, or write access beyond intended scope)

A system is affected if it runs any Ivanti Avalanche version below 6.3.3 with the Inforail Service enabled 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 Avalance to version 6.3.3 or later to receive the vendor patch for this SQL injection vulnerability. If immediate upgrade is not feasible, restrict network access to the Inforail Service and monitor for suspicious SQL patterns in service logs.

Recommended fix Moderate confidence

6.3.3

  1. 1. Back up the current Avalanche database and configuration files
  2. 2. Download Ivanti Avalanche version 6.3.3 or later from the official Ivanti support 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. Restart all Avalanche services
  6. 6. Verify the Inforail Service is running correctly
  7. 7. Test that the SQL injection vulnerability is no longer present
  8. 8. Monitor system logs for any unusual SQL activity
Caveat Review Ivanti release notes for any configuration or behavioral changes between your current version and 6.3.3

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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