dbcve.org
Connect SecureApplication · Ivanti

CVE-2024-37401

HIGH · 7.5 CVSS v3.0 Published 2024-12-12
Fix available
A fix is available. Upgrade to 22.7 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
An out-of-bounds read in IPsec of Ivanti Connect Secure before version 22.7R2.1 allows a remote unauthenticated attacker to cause a denial of service.

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

An out-of-bounds read vulnerability exists in the IPsec component of Ivanti Connect Secure before version 22.7R2.1. A remote unauthenticated attacker can trigger the vulnerability by sending specially crafted IPsec packets, causing the application to read memory outside allocated buffers, resulting in denial of service.

MitigationUpgrade Ivanti Connect Secure to version 22.7R2.1 or later. If immediate upgrade is not possible, consider restricting IPsec traffic at network perimeter or implementing IPS/IDS rules to detect anomalous IPsec traffic.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Verify IPsec is configured on the appliance
    Access the admin UI and navigate to IPsec configuration, or run 'show ipsec' via CLI to confirm IPsec tunnels or policies exist
    Affected if IPsec tunnels or policies are active - the vulnerability requires IPsec to be exposed to unauthenticated traffic
  2. Identify Ivanti Connect Secure version
    Log into the admin console, go to System > System Overview, or run 'show version' in CLI to display the installed software version
    Affected if The displayed version is 22.7 (any build) or any version below 22.7 (such as 22.6.x, 22.5.x, 9.x, etc.)
  3. Identify Ivanti Policy Secure version
    Log into the admin console, go to System > System Overview, or run 'show version' in CLI to display the installed software version
    Affected if The displayed version is 22.7 (any build) or any version below 22.7
  4. Confirm network exposure of IPsec service
    Review firewall rules or network configuration to determine if UDP port 500, UDP port 4500, or IPsec IKE ports are reachable from untrusted networks
    Affected if IPsec ports are exposed to the internet or untrusted external networks

You are affected if IPsec is enabled and your installed version of Ivanti Connect Secure or Ivanti Policy Secure is 22.7 or any version below 22.7; versions 22.7R2.1 and later are not affected.

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. If immediate upgrade is not possible, consider restricting IPsec traffic at network perimeter or implementing IPS/IDS rules to detect anomalous IPsec traffic.

Recommended fix High confidence

22.7R2.1 (or later)

  1. 1. Identify the current installed version of Ivanti Connect Secure or Policy Secure
  2. 2. If version is less than 22.7R2.1, plan for upgrade to 22.7R2.1 or later
  3. 3. Backup current configuration before performing upgrade
  4. 4. Download Ivanti Connect Secure 22.7R2.1 or later from the official Ivanti download portal
  5. 5. Apply the upgrade following Ivanti's standard upgrade procedure for your deployment type
  6. 6. Verify the upgrade was successful and the IPsec service is functioning properly
  7. 7. Confirm the new version is 22.7R2.1 or higher

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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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