dbcve.org
Connect SecureApplication · Ivanti

CVE-2024-22052

HIGH · 7.5 CVSS v3.1 Published 2024-04-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
A null pointer dereference vulnerability in IPSec component of Ivanti Connect Secure (9.x, 22.x) and Ivanti Policy Secure allows an unauthenticated malicious user to send specially crafted requests in-order-to crash the service thereby causing a DoS attack

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 null pointer dereference vulnerability in the IPSec component of Ivanti Connect Secure (9.x, 22.x) and Ivanti Policy Secure allows an unauthenticated attacker to crash the service via specially crafted requests, causing denial of service.

MitigationApply vendor patches for Ivanti Connect Secure and Policy Secure when available; until then, consider restricting network access to the IPSec service to trusted sources to reduce attack surface.

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= 22.1= 22.2= 22.3= 22.4= 22.5= 22.6
Policy SecureApplication
Affected:= 9.0= 9.1= 22.1= 22.2= 22.3= 22.4= 22.5= 22.6

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. Identify the installed Ivanti product
    Check the system or admin interface to determine if Ivanti Connect Secure or Ivanti Policy Secure is deployed. This can typically be found in the system information page, about section, or by running 'show system' in the admin CLI.
    Affected if The product is Ivanti Connect Secure version 9.1, 22.1, 22.2, 22.3, 22.4, 22.5, or 22.6, OR Ivanti Policy Secure version 9.0, 9.1, 22.1, 22.2, 22.3, 22.4, 22.5, or 22.6.
  2. Verify the exact version number
    Compare your installed version against the affected list. Use the admin web UI under System > Configuration > System Management > System Information, or use the CLI command 'show version' or 'cat /etc/version' if accessible.
    Affected if The installed version exactly matches any version listed in the affected products and versions.
  3. Confirm IPSec component is enabled
    Check if IPSec VPN functionality is configured on the appliance. In the admin UI, navigate to VPN > IPSec or use the CLI command 'show ipsec' to view IPSec status and configuration.
    Affected if IPSec is enabled or configured on the system (the vulnerability exists in the IPSec component).
  4. Check for service availability
    Verify the IPSec service is running and responsive. Attempt to access the admin interface or check service status via CLI commands such as 'show services' or by reviewing system logs for IPSec-related entries.
    Affected if The IPSec service is active and reachable via network.

You are affected if you are running Ivanti Connect Secure or Policy Secure with a version matching any of the listed affected versions AND the IPSec component is enabled and reachable on your network.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches for Ivanti Connect Secure and Policy Secure when available; until then, consider restricting network access to the IPSec service to trusted sources to reduce attack surface.

Recommended fix Moderate confidence

Ivanti Connect Secure 22.4+ or latest 22.x | Ivanti Policy Secure 22.3+ or latest 22.x

  1. 1. Identify the exact Ivanti product version currently deployed (Connect Secure or Policy Secure)
  2. 2. Consult Ivanti's official release notes and security advisories on forums.ivanti.com for CVE-2024-22052 specific patch information
  3. 3. For Ivanti Connect Secure: Upgrade to version 22.4 or later (or latest available 22.x release)
  4. 4. For Ivanti Policy Secure: Upgrade to version 22.3 or later (or latest available 22.x release)
  5. 5. For legacy 9.x installations: Upgrade to the latest 9.1Rx patch or consider migrating to supported 22.x release
  6. 6. After upgrade, verify the IPSec service runs normally and test IPSec VPN connectivity
  7. 7. Monitor forums.ivanti.com for any follow-up patch requirements
Caveat Legacy 9.x to 22.x upgrades may require configuration review; test thoroughly in staging before production deployment

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

Fix this in Connect Secure Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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