dbcve.org
Connect SecureApplication · Ivanti

CVE-2024-38649

HIGH · 7.5 CVSS v3.1 Published 2024-11-13
Fix available
A fix is available. Upgrade to 9.1 / 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 write in IPsec of Ivanti Connect Secure before version 22.7R2.1(Not Applicable to 9.1Rx) 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

A high-severity out-of-bounds write vulnerability exists in the IPsec component of Ivanti Connect Secure versions prior to 22.7R2.1. This memory corruption flaw can be exploited by a remote, unauthenticated attacker to cause a denial of service condition.

MitigationUpgrade Ivanti Connect Secure to version 22.7R2.1 or later to address the vulnerability. If immediate patching is not feasible, consider restricting IPsec-related network access or implementing additional firewall controls.

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

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.1/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. Confirm Ivanti Connect Secure is installed
    Identify if the target system is running Ivanti Connect Secure. This is typically an SSL VPN gateway product. Check the system hostname, admin web interface, or network service fingerprints for 'Ivanti Connect Secure' branding.
    Affected if The system is Ivanti Connect Secure and the IPsec component is in use.
  2. Determine installed version
    Access the admin web interface (System > Status or About page) or use the CLI command to display the software version. Look for a version string such as 9.x, 21.x, 22.x, or 22.7R2.1.
    Affected if The displayed version is lower than 22.7R2.1.
  3. Verify IPsec feature is configured
    Check the IPsec configuration through the admin UI (typically under VPN > IPsec or similar) or list active IPsec tunnels via CLI. Determine if any IPsec policies or tunnels are defined and active.
    Affected if IPsec tunnels or policies are actively configured on the device.
  4. Cross-reference version against vulnerable ranges
    Compare the installed version number to the affected ranges: versions less than 9.1, version 9.1 exactly, versions 21.9 through 22.7 inclusive. Any version below 22.7R2.1 that falls into these ranges is vulnerable.
    Affected if The installed version is < 9.1, = 9.1, >= 21.9 and < 22.7, or = 22.7.

The environment is affected if Ivanti Connect Secure is running with a version lower than 22.7R2.1 and the IPsec component is enabled or configured.

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

Upgrade Ivanti Connect Secure to version 22.7R2.1 or later to address the vulnerability. If immediate patching is not feasible, consider restricting IPsec-related network access or implementing additional firewall controls.

Recommended fix High confidence

22.7R2.1

  1. 1. Identify the current version of Ivanti Connect Secure by checking the admin console or using the system CLI command 'show version'
  2. 2. Navigate to the Ivanti support portal (forums.ivanti.com) and download version 22.7R2.1 or later
  3. 3. Review the upgrade instructions in the Ivanti Knowledge Base for Connect Secure
  4. 4. Back up the current configuration before upgrading
  5. 5. Apply the upgrade following the documented procedure (typically via the admin web interface or CLI)
  6. 6. After upgrade, verify the new version is installed using 'show version' command
  7. 7. Confirm the IPsec service is functioning properly
Caveat Review release notes for any configuration or feature changes between your current version and 22.7R2.1; test thoroughly in a non-production environment first

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
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
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,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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