dbcve.org
Connect SecureApplication · Ivanti

CVE-2024-11633

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
Argument injection in Ivanti Connect Secure before version 22.7R2.4 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

Ivanti Connect Secure versions prior to 22.7R2.4 contain an argument injection vulnerability. A remote attacker with admin-level authentication can inject arbitrary arguments into system commands, leading to remote code execution on the affected appliance.

MitigationUpgrade Ivanti Connect Secure to version 22.7R2.4 or later to remediate this vulnerability. Restrict admin access to trusted personnel and monitor for unauthorized administrative sessions.

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

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 if Ivanti Connect Secure is running
    Access the appliance admin interface or check system documentation for the product name. Look for login pages with 'Ivanti Connect Secure' branding.
    Affected if The system is running Ivanti Connect Secure as the VPN/secure access gateway.
  2. Determine the installed version
    Log into the admin console and navigate to System > Configuration > System Management > Version Info, or check the login page footer for version display.
    Affected if The displayed version is 22.7 (any build) or any version prior to 22.7 (such as 22.6.x, 22.5.x, 9.x, etc.).
  3. Verify admin interface exposure
    Check network access controls, firewall rules, or VPN policies to determine if the admin interface (typically port 443 or 8443) is accessible from untrusted networks.
    Affected if The admin interface is accessible from the internet or untrusted networks without strong access controls.
  4. Review admin user sessions and access logs
    Check System > Logs > Admin Sessions or similar logging sections for concurrent admin logins, unusual session origins, or commands executed by administrators.
    Affected if There are unexpected admin sessions, sessions from unknown IP addresses, or suspicious commands in admin logs.
  5. Check for unauthorized changes or backdoors
    Review system configuration backups, user account listings, and scheduled tasks for unexpected modifications or new accounts.
    Affected if New admin accounts were created, scheduled tasks were added, or configuration changes occurred without documented approval.

You are affected if Ivanti Connect Secure version 22.7 or any version prior to 22.7 is running AND the admin interface is accessible to untrusted users.

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 to remediate this vulnerability. Restrict admin access to trusted personnel and monitor for unauthorized administrative sessions.

Recommended fix High confidence

Ivanti Connect Secure version 22.7R2.4 or later

  1. 1. Back up the current Ivanti Connect Secure configuration before proceeding with any upgrade
  2. 2. Download Ivanti Connect Secure version 22.7R2.4 or a later stable release from the official Ivanti support portal (forums.ivanti.com)
  3. 3. Upload the upgrade package through the admin console or CLI following Ivanti's standard upgrade procedures
  4. 4. Verify the upgrade completes successfully and the system restarts normally
  5. 5. Confirm the running version displays as 22.7R2.4 or higher post-upgrade
  6. 6. Validate that the administrative interface is accessible and the previously working configurations are intact
Caveat Review Ivanti release notes for any configuration changes or deprecated features between your current version and 22.7R2.4

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

Fix this in Connect Secure Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
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,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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