dbcve.org
Connect SecureApplication · Ivanti

CVE-2024-38655

HIGH · 7.2 CVSS v3.1 Published 2024-11-13
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.1 and 9.1R18.9 and Ivanti Policy Secure before version 22.7R1.1 and 9.1R18.9 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 (before 22.7R2.1 and 9.1R18.9) and Ivanti Policy Secure (before 22.7R1.1 and 9.1R18.9) allows a remote authenticated attacker with admin privileges to inject malicious arguments that result in remote code execution.

MitigationUpgrade Ivanti Connect Secure to version 22.7R2.1 or 9.1R18.9 or later, and Ivanti Policy Secure to version 22.7R1.1 or 9.1R18.9 or later. Since the attacker requires admin privileges, ensure admin accounts use strong, unique passwords and consider implementing multi-factor authentication.

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 product and version
    Determine if the system is running Ivanti Connect Secure or Ivanti Policy Secure, then check the installed version number. This is typically visible in the admin console or system information page.
    Affected if The product is Ivanti Connect Secure version < 22.7 or = 22.7, or Ivanti Policy Secure version < 22.7 or = 22.7, and the version is earlier than the fixed releases (22.7R2.1 or 9.1R18.9 for Connect Secure; 22.7R1.1 or 9.1R18.9 for Policy Secure).
  2. Verify admin account accessibility
    Review the admin user accounts configured on the Ivanti appliance. Check whether remote admin access is enabled and whether admin credentials could be obtained by an external attacker.
    Affected if Remote admin access is enabled and admin accounts exist, providing a potential attack vector for an authenticated attacker.
  3. Confirm admin privilege configuration
    Examine which accounts hold administrative privileges in the Ivanti admin panel. An attacker with admin-level access is required to exploit this vulnerability.
    Affected if Any admin-level accounts are present and accessible, satisfying the privilege requirement for this CVE.
  4. Compare against fixed version ranges
    Review the currently installed version against the known vulnerable and fixed version ranges provided in the CVE documentation.
    Affected if The installed version is one of the vulnerable versions (any version < 22.7 or exactly 22.7 for either product) and is not updated to the patched releases (22.7R2.1/9.1R18.9 for Connect Secure; 22.7R1.1/9.1R18.9 for Policy Secure).

The environment is affected if the system is running Ivanti Connect Secure or Policy Secure at version 22.7 or earlier without the security patches applied, and admin-level accounts are 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.1 or 9.1R18.9 or later, and Ivanti Policy Secure to version 22.7R1.1 or 9.1R18.9 or later. Since the attacker requires admin privileges, ensure admin accounts use strong, unique passwords and consider implementing multi-factor authentication.

Recommended fix High confidence

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

  1. 1. Identify the exact version of Ivanti Connect Secure or Policy Secure currently installed
  2. 2. Download the appropriate fixed version from Ivanti's official support portal: 22.7R2.1 or 9.1R18.9 for Connect Secure; 22.7R1.1 or 9.1R18.9 for Policy Secure
  3. 3. Review Ivanti upgrade documentation and release notes for pre-upgrade requirements
  4. 4. Create a full backup of the current configuration
  5. 5. Schedule a maintenance window as upgrades may require downtime
  6. 6. Perform the upgrade following Ivanti's official upgrade procedure
  7. 7. After upgrade, verify the new version is installed correctly
  8. 8. Confirm the vulnerability is remediated by checking the version number
Caveat Review release notes for any behavioral changes or deprecated features between your current version and the target fixed version; some upgrades may require specific migration steps

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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