CVE-2024-21894
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 · uneditedA heap overflow 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. In certain conditions this may lead to execution of arbitrary code
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 confidenceA heap overflow vulnerability in the IPSec component of Ivanti Connect Secure (9.x, 22.x) and Ivanti Policy Secure allows an unauthenticated remote attacker to send specially crafted requests that can crash the service (denial of service) and potentially achieve arbitrary code execution in certain conditions.
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= 9.1= 22.1= 22.2= 22.3= 22.4= 22.5= 22.6= 9.0= 9.1= 22.1= 22.2= 22.3= 22.4= 22.5= 22.6CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Ivanti productCheck system information or product documentation to determine if the machine is running Ivanti Connect Secure or Ivanti Policy SecureAffected if The product is Connect Secure or Policy Secure and the version matches the affected list (9.0, 9.1, 22.1-22.6)
-
Verify the exact software versionAccess the admin console or use system commands to retrieve the installed version number (typically found in About or System Status pages)Affected if The installed version equals 9.1, 22.1, 22.2, 22.3, 22.4, 22.5, or 22.6 for Connect Secure; or 9.0, 9.1, 22.1-22.6 for Policy Secure
-
Confirm IPSec feature is enabledReview the VPN or IPSec configuration settings in the admin interface to determine if IPSec tunnels or services are actively configuredAffected if IPSec is enabled and configured on the system
-
Inspect for service crashes or instabilityCheck system logs, VPN daemon logs, or service status for sudden restarts, core dumps, or crash reports related to the IPSec componentAffected if The IPSec service has crashed, restarted unexpectedly, or shows heap-related error messages in logs
-
Review network exposure of IPSec serviceCheck firewall rules or access lists to determine if the IPSec ports (500, 4500, ESP protocol) are exposed to untrusted networksAffected if IPSec services are reachable from external/untrusted networks without adequate filtering
The environment is affected if Ivanti Connect Secure (9.1 or 22.x) or Ivanti Policy Secure (9.0-9.1 or 22.x) is installed with IPSec enabled, and the version matches any of the listed affected versions.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply vendor-released patches for CVE-2024-21894 immediately; if patching is delayed, restrict network exposure of the IPSec service and monitor for indicators of compromise.
- Consultation6.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,296.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21894 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-21894 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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