dbcve.org
Connect SecureApplication · Ivanti

CVE-2024-9420

HIGH · 8.8 CVSS v3.1 Published 2024-11-12
Fix available
A fix is available. Upgrade to 9.1 / 22.7 or later.
See remediation →
94/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
A use-after-free in Ivanti Connect Secure before version 22.7R2.3 and 9.1R18.9 and Ivanti Policy Secure before version 22.7R1.2 allows a remote authenticated attacker 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

A use-after-free vulnerability in the authentication handling of Ivanti Connect Secure and Policy Secure allows a remote authenticated attacker to execute arbitrary code. The vulnerability stems from improper memory management where memory is accessed after being freed, leading to potential code execution.

MitigationApply vendor-supplied patches by upgrading Ivanti Connect Secure to version 22.7R2.3 or later (9.1R18.9 for branch) and Ivanti Policy Secure to version 22.7R1.2 or later. Coordinate a maintenance window for the upgrade and validate functionality post-patch.

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:< 9.1>= 21.9, < 22.7= 9.1= 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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
    Check the system or admin interface to determine if Ivanti Connect Secure or Ivanti Policy Secure is deployed
    Affected if Neither product is identified (not an affected product)
  2. Determine the installed version of Ivanti Connect Secure
    Access the admin console or run: 'show version' command via CLI/SSH, or check the system information page in the web interface
    Affected if Version is < 9.1, OR >= 21.9 AND < 22.7, OR equals 9.1, OR equals 22.7 (vulnerable version)
  3. Determine the installed version of Ivanti Policy Secure
    Access the admin console or run: 'show version' command via CLI/SSH, or check the system information page in the web interface
    Affected if Version is < 22.7 OR equals 22.7 (vulnerable version)
  4. Verify authentication module is enabled
    Check the system configuration for authentication handlers - confirm that user authentication is configured and active in the system settings
    Affected if Authentication is not enabled (vulnerability not exploitable as described)
  5. Compare version against safe releases
    Note the exact version number. Safe versions per vendor: Connect Secure 22.7R2.3+, 9.1R18.9+; Policy Secure 22.7R1.2+
    Affected if Running any version below these fixed releases

You are affected if you are running Ivanti Connect Secure or Policy Secure with an authentication module enabled and the installed version falls within the vulnerable ranges listed.

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 9.1 / 22.7 or later
Fixed in 9.122.7
Interim mitigation

Apply vendor-supplied patches by upgrading Ivanti Connect Secure to version 22.7R2.3 or later (9.1R18.9 for branch) and Ivanti Policy Secure to version 22.7R1.2 or later. Coordinate a maintenance window for the upgrade and validate functionality post-patch.

Recommended fix High confidence

Ivanti Connect Secure: 22.7R2.3 (or 9.1R18.9); Ivanti Policy Secure: 22.7R1.2

  1. 1. Identify the current installed version of Ivanti Connect Secure or Ivanti Policy Secure by checking the system administration interface or using the CLI command 'show version'
  2. 2. For Ivanti Connect Secure users: Upgrade to version 22.7R2.3 or later, OR upgrade to version 9.1R18.9 or later depending on your release branch
  3. 3. For Ivanti Policy Secure users: Upgrade to version 22.7R1.2 or later
  4. 4. After upgrading, verify the new version is running by checking 'show version' in the admin CLI
  5. 5. Test critical business workflows to ensure the upgrade did not break existing functionality
  6. 6. Review the Ivanti knowledge base at forums.ivanti.com for any known post-upgrade issues or configuration changes
Caveat Review release notes for any deprecated features or required migration steps before upgrading

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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,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 $3,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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