dbcve.org
Connect SecureApplication · Ivanti

CVE-2024-11634

HIGH · 7.2 CVSS v3.1 Published 2024-12-10
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
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)

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

Command injection vulnerability in Ivanti Connect Secure (before 22.7R2.3) and Ivanti Policy Secure (before 22.7R1.2) allows a remote authenticated attacker with admin privileges to achieve remote code execution by injecting arbitrary commands through the web interface or administrative API.

MitigationUpgrade Ivanti Connect Secure to version 22.7R2.3 or later and Ivanti Policy Secure to version 22.7R1.2 or later. Limit admin access to trusted personnel only and monitor for suspicious administrative activity.

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
    Access the admin web interface or check system documentation to determine if the device is running Ivanti Connect Secure or Ivanti Policy Secure
    Affected if The device is running either product and the version falls within the affected range
  2. Determine the installed version
    Log into the admin web interface and navigate to the System > Status or Help > About page to view the exact firmware version
    Affected if The version is 22.7 or lower for either product (exact version numbers below 22.7 or exactly 22.7)
  3. Confirm admin web interface or API access is enabled
    Check the device configuration to verify that the administrative web interface or API is accessible (typically on ports 443, 8443, or configured admin URLs)
    Affected if The web interface or administrative API is enabled and reachable from network locations where attackers could authenticate
  4. Review admin account activity logs
    Examine authentication and admin action logs for any unauthorized or suspicious admin sessions, especially those originating from unexpected IP addresses or occurring at unusual times
    Affected if There are admin login attempts or commands from untrusted sources or unauthorized users

A user is affected if they are running Ivanti Connect Secure version 22.7 or lower, or Ivanti Policy Secure version 22.7 or lower, with the admin web interface or API enabled and accessible.

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.3 or later and Ivanti Policy Secure to version 22.7R1.2 or later. Limit admin access to trusted personnel only and monitor for suspicious administrative activity.

Recommended fix High confidence

Ivanti Connect Secure 22.7R2.3+ or Ivanti Policy Secure 22.7R1.2+

  1. Identify whether the affected system is Ivanti Connect Secure or Ivanti Policy Secure.
  2. For Ivanti Connect Secure: Upgrade to version 22.7R2.3 or later.
  3. For Ivanti Policy Secure: Upgrade to version 22.7R1.2 or later.
  4. After upgrading, verify the command injection vulnerability is remediated by reviewing system logs and confirming no unauthorized command execution attempts.
  5. Ensure the admin user account used for the attack is reviewed for any unauthorized changes or additional accounts created.

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
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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