Security Resilience

CVE-2024-11634

RCE in Ivanti Connect Secure ≤ 22.7

Published
10 December 2024
Modified
17 January 2025
Patch / advisory
CVSS Score v3.1 9.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
EPSS Score 0.018 79th percentile
Risk Priority 71 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-11634 is a critical-severity Command Injection (CWE-77) vulnerability in Ivanti Connect Secure. Its CVSS base score is 9.1 (Critical).

Operationally, ranked in the top 21% 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.

CVE-2024-11634 is a command injection vulnerability, tracked under CWE-77, that affects Ivanti Connect Secure prior to version 22.7R2.3 and Ivanti Policy Secure prior to version 22.7R1.2. The flaw is not applicable to the 9.1Rx branch. It carries a CVSS 3.1 base score of 9.1, reflecting a network-accessible attack with low complexity that requires high privileges yet can impact confidentiality, integrity, and availability across security boundaries.

A remote authenticated attacker holding administrative privileges can supply crafted input that results in arbitrary command execution on the affected appliance, enabling full remote code execution.

The December 2024 Ivanti security advisory provides official guidance on affected releases and remediation steps for both products.

EPSS for the CVE reached a peak of 0.2131 after disclosure before settling at the current value of 0.1423, indicating a clear rise in exploitation interest that warrants renewed attention from defenders.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Command injection in Ivanti Connect Secure before version 22.7R2.3 and Ivanti Policy Secure before version 22.7R1.2 allows a remote authenticated attacker with admin privileges to achieve remote code execution. (Not applicable to 9.1Rx)

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-21887Same product: Ivanti Connect Secure
CVE-2024-37401Same product: Ivanti Connect Secure
CVE-2024-13830Same product: Ivanti Connect Secure
CVE-2024-39711Same product: Ivanti Connect Secure
CVE-2024-8495Same product: Ivanti Connect Secure
CVE-2020-8243Same product: Ivanti Connect Secure
CVE-2024-39712Same product: Ivanti Connect Secure
CVE-2024-47905Same product: Ivanti Connect Secure
CVE-2024-11006Same product: Ivanti Connect Secure
CVE-2024-12058Same product: Ivanti Connect Secure

Affected Assets

ivanti
connect secure
22.7 · ≤ 22.7
ivanti
policy secure
22.7 · ≤ 22.7

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