Cyber Resilience

CVE-2021-42132

RCE in Ivanti Avalanche ≤ 6.3.3

High EPSSRCECommand Injection
Published
07 December 2021
Modified
21 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.70 99.3th percentile
Risk Priority 87 floored blend · peak EPSS

Summary

CVE-2021-42132 is a high-severity Command Injection (CWE-77) vulnerability in Ivanti Avalanche. Its CVSS base score is 8.8 (High).

Operationally, ranked in the top 0.7% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

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.

CWE(s)
CWE-77

Related Threats

Likely ATT&CK TechniquesAI

Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.

T1059 Command and Scripting Interpreter Executionconfidence: HIGH
Command injection in the Inforail Service directly enables arbitrary command execution on the target system.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Accessconfidence: HIGH
The vulnerability is in a network-exposed service (Inforail), allowing remote attackers to execute commands via the exposed interface.
attack.mitre.org →
inferred from description + CWE · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2021-42129Same product: Ivanti Avalanche
CVE-2024-22061Same product: Ivanti Avalanche
CVE-2024-50331Same product: Ivanti Avalanche
CVE-2024-27984Same product: Ivanti Avalanche
CVE-2021-42127Same product: Ivanti Avalanche
CVE-2021-42125Same product: Ivanti Avalanche
CVE-2024-47010Same product: Ivanti Avalanche
CVE-2025-8297Same product: Ivanti Avalanche
CVE-2024-24995Same product: Ivanti Avalanche
CVE-2024-50321Same product: Ivanti Avalanche

Affected Assets

ivanti
avalanche
≤ 6.3.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.2.3
  • V1.2.5
  • V1.2.8
  • V1.2.9

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and neutralization that prevent command injection.

DE.CM-09 partial match
prevents

Runtime monitoring of software and data can detect anomalous command execution resulting from injection.

ID.RA-01 partial match
prevents

Identifying recorded vulnerabilities enables remediation of command-injection flaws before exploitation.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.28 Secure coding mostly match
prevents

Secure coding standards require proper escaping and parameterization of commands, directly eliminating CWE-77.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing in development catches command-injection vulnerabilities before release.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and command construction practices that directly prevent command injection.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for controls against injection flaws including command injection.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce the attack surface but do not prescribe the specific neutralization techniques needed.

A.8.31 Separation of development, test and production environments none match
none

Environment separation limits the blast radius of an exploited command injection but does not prevent the flaw itself.

References