dbcve.org
Connect SecureApplication · Ivanti

CVE-2024-37400

HIGH · 7.5 CVSS v3.0 Published 2024-11-13
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 Ivanti Connect Secure before version 22.7R2.3 allows a remote unauthenticated attacker to trigger an infinite loop, causing 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

Ivanti Connect Secure before version 22.7R2.3 contains an out-of-bounds read vulnerability that allows remote unauthenticated attackers to trigger an infinite loop in the affected component, resulting in denial of service.

MitigationUpgrade Ivanti Connect Secure to version 22.7R2.3 or later to remediate this vulnerability.

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

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. Identify Ivanti Connect Secure installation
    Access the admin console or check system information page to find the installed version number. This is typically visible in the web interface under System > Status or in the about page.
    Affected if The displayed version is 22.7 or any version lower than 22.7 (including all 9.x and earlier releases)
  2. Compare version against affected range
    Document the exact version number (for example: 22.6, 22.5, 22.4, 9.x, etc.) and check if it falls within < 22.7 or exactly equals 22.7.
    Affected if The version is 22.7 or any version below 22.7, meaning it is vulnerable
  3. Confirm the service is network accessible
    Verify that Ivanti Connect Secure is reachable over the network on the admin or gateway ports (typically ports 443, 8443, or configured HTTPS ports). This can be confirmed by attempting to access the login page from a remote system or reviewing network listener configurations.
    Affected if The service is exposed on the network, making it reachable for remote unauthenticated attackers
  4. Review SSL VPN gateway status
    Check if the SSL VPN gateway service is enabled and running. This is typically viewable in the admin console under Configuration > SSL VPN Settings or in the system service status.
    Affected if The SSL VPN gateway service is enabled, as this is the affected component that processes unauthenticated requests

If the installed Ivanti Connect Secure version is 22.7 or any version below 22.7 and the service is network-accessible, the environment is vulnerable to remote denial of service via the infinite loop triggered by unauthenticated attackers.

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.3 or later to remediate this vulnerability.

Recommended fix High confidence

22.7R2.3

  1. Download Ivanti Connect Secure version 22.7R2.3 from the official Ivanti download portal
  2. Review Ivanti upgrade documentation for pre-upgrade requirements and backup procedures
  3. Apply the upgrade to Ivanti Connect Secure, following standard upgrade procedures
  4. Verify the upgrade was successful and the version shows 22.7R2.3
  5. Test that the VPN gateway is functioning normally

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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