dbcve.org
Connect SecureApplication · Ivanti

CVE-2024-10644

HIGH · 7.2 CVSS v3.1 Published 2025-02-11
Fix available
A fix is available. Upgrade to 22.7 or later.
See remediation →
78/100
Remediation priority · High
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
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.

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 · high confidence

Code injection vulnerability in Ivanti Connect Secure (versions before 22.7R2.4) and Ivanti Policy Secure (versions before 22.7R1.3) allows remote authenticated attackers with admin privileges to inject and execute arbitrary code on the affected systems.

MitigationUpgrade Ivanti Connect Secure to version 22.7R2.4 or later, and Ivanti Policy Secure to version 22.7R1.3 or later. Apply within the SLA window given the high-severity rating and RCE impact.

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
Connect SecureApplication
Affected:< 22.7= 22.7
Policy SecureApplication
Affected:< 22.7= 22.7

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 the installed Ivanti product
    Determine whether the system is running Ivanti Connect Secure or Ivanti Policy Secure. This can typically be found in the product web interface header, system information page, or by querying the system directly.
    Affected if The system is running either Ivanti Connect Secure or Ivanti Policy Secure.
  2. Retrieve the installed version number
    Locate the version information in the admin web interface under System > System Management > System Information, or use the CLI command 'show version' if available.
    Affected if The exact version number cannot be determined.
  3. Compare version against affected ranges for Connect Secure
    If Ivanti Connect Secure is installed, compare the installed version to: versions before 22.7R2.4, or exactly version 22.7 (including 22.7R1, 22.7R2, 22.7R2.1, 22.7R2.2, 22.7R2.3).
    Affected if The installed version is 22.7, or any 22.7.x version before 22.7R2.4.
  4. Compare version against affected ranges for Policy Secure
    If Ivanti Policy Secure is installed, compare the installed version to: versions before 22.7R1.3, or exactly version 22.7 (including 22.7R1, 22.7R1.1, 22.7R1.2).
    Affected if The installed version is 22.7, or any 22.7R1.x version before 22.7R1.3.
  5. Verify admin access exists
    Determine whether the admin web interface is accessible and confirm that admin user accounts are configured. The vulnerability requires an authenticated admin user to exploit.
    Affected if The admin interface is exposed and admin accounts exist.

The environment is affected if running Ivanti Connect Secure version 22.7 through 22.7R2.3, or Ivanti Policy Secure version 22.7 through 22.7R1.2, with the admin interface accessible and admin accounts configured.

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 22.7 or later
Fixed in 22.7
Interim mitigation

Upgrade Ivanti Connect Secure to version 22.7R2.4 or later, and Ivanti Policy Secure to version 22.7R1.3 or later. Apply within the SLA window given the high-severity rating and RCE impact.

Recommended fix High confidence

Ivanti Connect Secure: 22.7R2.4 or later; Ivanti Policy Secure: 22.7R1.3 or later

  1. Identify whether the deployed product is Ivanti Connect Secure or Ivanti Policy Secure
  2. Check current version of the Ivanti product using the admin console or system information
  3. For Ivanti Connect Secure: Upgrade to version 22.7R2.4 or later
  4. For Ivanti Policy Secure: Upgrade to version 22.7R1.3 or later
  5. After upgrade, verify the new version is correctly installed
  6. Review admin access controls and consider limiting admin privilege assignment as a defense-in-depth measure
Caveat Review Ivanti release notes for any configuration or behavioral changes between versions before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Connect Secure Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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