What is the CVSS score of CVE-2024-10644?

CVE-2024-10644 has a CVSS 3.1 base score of 9.1 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H. EPSS exploitation probability: 6.8%.

Which versions of Connect Secure are affected by CVE-2024-10644?

Organizations using Ivanti Connect Secure face critical risk from CVE-2024-10644, a code injection vulnerability rated CVSS 9.1.

How to fix or mitigate CVE-2024-10644?

Within 24 hours: Identify all affected systems running Ivanti Connect Secure and apply vendor patches immediately. Validate that input sanitization is in place for all user-controlled parameters.

Connect Secure CVE-2024-10644

CRITICAL

Code Injection (CWE-94)

2025-02-11 3c1d8aa1-5a33-4ea4-8992-aadd6440af75

RCE Code Injection Ivanti Connect Secure Policy Secure

9.1

CVSS 3.1

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Mar 28, 2026 - 18:26 vuln.today

CVE Published

Feb 11, 2025 - 16:15 nvd

CRITICAL 9.1

DescriptionNVD

AnalysisAI

Code injection in Ivanti Connect Secure before version 22.7R2.4 and Ivanti Policy Secure before version 22.7R1.3 allows a remote authenticated attacker with admin privileges to achieve remote code. Rated critical severity (CVSS 9.1), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.

Technical ContextAI

This vulnerability is classified as Code Injection (CWE-94), which allows attackers to inject and execute arbitrary code within the application. Code injection in Ivanti Connect Secure before version 22.7R2.4 and Ivanti Policy Secure before version 22.7R1.3 allows a remote authenticated attacker with admin privileges to achieve remote code execution. Affected products include: Ivanti Connect Secure, Ivanti Policy Secure. Version information: version 22.7.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Never evaluate user-controlled input as code. Use sandboxing, disable dangerous functions, apply strict input validation.