dbcve.org
Connect SecureApplication · Ivanti

CVE-2024-11007

HIGH · 7.2 CVSS v3.1 Published 2024-11-12
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.1 (Not Applicable to 9.1Rx) and Ivanti Policy Secure before version 22.7R1.1 (Not Applicable to 9.1Rx) 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

Command injection vulnerability in Ivanti Connect Secure and Policy Secure allows an authenticated attacker with admin privileges to inject arbitrary OS commands and achieve remote code execution. The vulnerability exists in versions prior to 22.7R2.1 (Connect Secure) and 22.7R1.1 (Policy Secure).

MitigationUpgrade Ivanti Connect Secure to version 22.7R2.1 or later and Ivanti Policy Secure to version 22.7R1.1 or later. Restrict admin access to trusted networks and monitor for unauthorized admin 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
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 Ivanti product
    Log into the admin web interface and locate the product name on the dashboard or system information page, or run 'show system-information' in the CLI
    Affected if The product is Ivanti Connect Secure or Ivanti Policy Secure
  2. Check the installed version
    In the admin interface, go to System > Configuration > System Information, or run 'show version' in the CLI to view the exact firmware version
    Affected if The version is < 22.7 or equals 22.7 (any 22.7.x release before 22.7R2.1 for Connect Secure or before 22.7R1.1 for Policy Secure)
  3. Confirm admin access exists
    Check for existing admin user accounts in the admin interface under Users > Administrators or by running 'show administrators' in the CLI
    Affected if Any admin-level account exists on the system, which would allow exploitation if the attacker obtains credentials

The environment is affected if running Ivanti Connect Secure version 22.7 or any version below 22.7, or Ivanti Policy Secure version 22.7 or any version below 22.7, with admin accounts present.

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.1 or later and Ivanti Policy Secure to version 22.7R1.1 or later. Restrict admin access to trusted networks and monitor for unauthorized admin sessions.

Recommended fix High confidence

Connect Secure: upgrade to 22.7R2.1 or later; Policy Secure: upgrade to 22.7R1.1 or later

  1. 1. Identify the currently installed version of Ivanti Connect Secure or Ivanti Policy Secure via the admin console or system diagnostics
  2. 2. If running Connect Secure version < 22.7 or = 22.7, plan upgrade to version 22.7R2.1 or later
  3. 3. If running Policy Secure version < 22.7 or = 22.7, plan upgrade to version 22.7R1.1 or later
  4. 4. Review release notes and upgrade documentation from Ivanti for prerequisites and compatibility requirements
  5. 5. Test the upgrade in a non-production environment first to validate functionality
  6. 6. Apply the upgrade in production following standard change management procedures
  7. 7. Verify successful installation by checking the new version number in the admin interface
  8. 8. Confirm the command injection vulnerability is remediated by reviewing system logs and running security validation tests
Caveat Review Ivanti release notes for any feature changes or migration considerations before upgrading; this fix does not apply to 9.1Rx versions which are noted as not affected

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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