dbcve.org
Connect SecureApplication · Ivanti

CVE-2024-39712

CRITICAL · 9.1 CVSS v3.0 Published 2024-11-13
Fix available
A fix is available. Upgrade to 22.7 or later.
See remediation →
97/100
Remediation priority · Urgent
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.1 and 9.1R18.7 and Ivanti Policy Secure before version 22.7R1.1 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

Argument injection vulnerability in Ivanti Connect Secure and Policy Secure gateways allows remote authenticated attackers with admin privileges to inject arbitrary arguments into system commands, leading to remote code execution. This is a critical command injection flaw affecting VPN and policy enforcement appliances.

MitigationUpgrade Ivanti Connect Secure to version 22.7R2.1 or 9.1R18.7 (or later), and Ivanti Policy Secure to version 22.7R1.1 (or later). Also review admin access logs for signs of compromise and ensure admin accounts use strong, unique credentials.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/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
    Access the admin console or check the system information page to determine if the appliance is Ivanti Connect Secure or Ivanti Policy Secure
    Affected if Product is Connect Secure or Policy Secure with version < 22.7 or = 22.7
  2. Check the installed version
    Log into the admin interface and navigate to System > Administration > System Information, or run 'show version' via CLI, to confirm the exact firmware version
    Affected if Version is less than 22.7 or exactly 22.7
  3. Verify admin access is enabled
    Confirm that the admin web interface or SSH admin access is enabled and accessible. Check System > Administration > Admin Users to list configured admin accounts
    Affected if Admin interface is accessible with valid admin credentials, allowing authenticated admin sessions
  4. Review admin access logs
    Navigate to System > Logs > Admin Access Logs or equivalent log section to review recent admin login events and command activity for signs of unauthorized admin usage
    Affected if Unexpected admin logins, commands, or configuration changes are present in logs

The environment is affected if Ivanti Connect Secure or Policy Secure is running version 22.7 or any version below 22.7 and the admin interface is accessible with valid admin credentials.

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 9.1R18.7 (or later), and Ivanti Policy Secure to version 22.7R1.1 (or later). Also review admin access logs for signs of compromise and ensure admin accounts use strong, unique credentials.

Recommended fix High confidence

Ivanti Connect Secure: upgrade to 22.7R2.1 (or 9.1R18.7); Ivanti Policy Secure: upgrade to 22.7R1.1

  1. 1. Identify the exact currently installed version of Ivanti Connect Secure or Ivanti Policy Secure
  2. 2. For Ivanti Connect Secure: Download version 22.7R2.1 (or 9.1R18.7 for the 9.x branch) from the Ivanti support portal
  3. 3. For Ivanti Policy Secure: Download version 22.7R1.1 from the Ivanti support portal
  4. 4. Review Ivanti upgrade documentation and release notes for pre-upgrade requirements
  5. 5. Create a full system backup or snapshot before proceeding
  6. 6. Schedule a maintenance window as upgrades may cause temporary service interruption
  7. 7. Upload the upgrade package via the admin web interface or CLI
  8. 8. Execute the upgrade and verify the system boots successfully
Caveat Review release notes for any configuration changes or deprecated features; some older browser versions may no longer be supported for admin access

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
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
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,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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