Security Resilience

CVE-2024-22061

RCE in Ivanti Avalanche ≤ 6.4.3.528

Published
19 April 2024
Modified
06 May 2025
Patch / advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.036 89th percentile
Risk Priority 80 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-22061 is a critical-severity Command Injection (CWE-77) vulnerability in Ivanti Avalanche. Its CVSS base score is 9.8 (Critical).

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

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

A Heap Overflow vulnerability exists in the WLInfoRailService component of Ivanti Avalanche versions prior to 6.4.3. The flaw, tracked as CVE-2024-22061 with a CVSS score of 9.8 and associated with CWE-77, permits remote unauthenticated attackers to execute arbitrary commands on affected systems.

An attacker with network access can exploit the issue without authentication or user interaction, achieving full compromise through command execution that impacts confidentiality, integrity, and availability. The attack vector is rated as network-accessible with low complexity under the CVSS metrics.

The vendor advisory for Avalanche 6.4.3 details security hardening measures and addresses this CVE along with related issues, indicating that upgrading to version 6.4.3 mitigates the vulnerability. The associated EPSS score reached a peak of 0.0919 before receding to the current value of 0.0499.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A Heap Overflow vulnerability in WLInfoRailService component of Ivanti Avalanche before 6.4.3 allows a remote unauthenticated attacker to execute arbitrary commands

CWE(s)

Related Threats

CVEs Like This One

CVE-2021-42132Same product: Ivanti Avalanche
CVE-2021-42129Same product: Ivanti Avalanche
CVE-2023-38036Same product: Ivanti Avalanche
CVE-2024-24998Same product: Ivanti Avalanche
CVE-2023-28126Same product: Ivanti Avalanche
CVE-2024-23528Same product: Ivanti Avalanche
CVE-2022-36981Same product: Ivanti Avalanche
CVE-2023-28125Same product: Ivanti Avalanche
CVE-2024-47011Same product: Ivanti Avalanche
CVE-2023-41474Same product: Ivanti Avalanche

Affected Assets

ivanti
avalanche
≤ 6.4.3.528

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover command-construction flaws before deployment.

Input validation directly stops construction of commands from untrusted data containing special elements.

Secure engineering principles include proper neutralization and safe command construction practices.

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.

blocks

A.8.25 mandates secure SDLC practices including secure coding guidelines, security requirements, checkpoints, testing (scans/penetration), and developer training that reduce command injection defects, but leaves a minority slice (e.g. incomplete implementation of those practices, outsourced development without full assurance, or post-SDLC changes) where the weakness can still arise and be exploitable.

blocks

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

blocks

A.8.27 mandates security-by-design principles (e.g. distrust external input, secure session control, data validation/sanitization, least privilege) and design reviews that can stop command injection from being introduced, but this is only a minority slice of CWE-77 because the weakness can still arise in code that bypasses those principles, in non-reviewed components, or in runtime injection vectors the architecture review does not reach.

prevents

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

finds

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

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-77, a class-level weakness, and none of its children carries one either.

References