dbcve.org
Connect SecureApplication · Ivanti

CVE-2024-37404

HIGH · 8.8 CVSS v3.1 Published 2024-10-18
Fix available
A fix is available. Upgrade to 9.1 / 22.7 or later.
See remediation →
94/100
Remediation priority · Urgent
High EPSS Remotely reachable Zero-click Patch available

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
Improper Input Validation in the admin portal of Ivanti Connect Secure before 22.7R2.1 and 9.1R18.9, or Ivanti Policy Secure before 22.7R1.1 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

A detailed technical summary for this CVE is being prepared.

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>= 22.3, < 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

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
Vendor patch forums.ivanti.com →
Recommended fix High confidence

Ivanti Connect Secure 9.1R18.9+ or 22.7R2.1+; Ivanti Policy Secure 22.7R1.1+

  1. 1. Identify the current version of Ivanti Connect Secure or Policy Secure by accessing the admin console or system information page
  2. 2. Determine which product and version branch you are running (Connect Secure 9.x, Connect Secure 22.x, or Policy Secure)
  3. 3. For Ivanti Connect Secure 9.x: Upgrade to version 9.1R18.9 or later
  4. 4. For Ivanti Connect Secure 22.x: Upgrade to version 22.7R2.1 or later
  5. 5. For Ivanti Policy Secure: Upgrade to version 22.7R1.1 or later
  6. 6. Download the appropriate update from the official Ivanti download portal or support site
  7. 7. Apply the upgrade following Ivanti's standard upgrade procedures documented in the admin guide
  8. 8. After upgrade, verify the version change in the admin console under System > Status
Caveat Review Ivanti release notes for the target version to check for any configuration or feature changes that may require adjustment

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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