dbcve.org
Connect SecureApplication · Ivanti

CVE-2024-8495

HIGH · 7.5 CVSS v3.1 Published 2024-11-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
A null pointer dereference in Ivanti Connect Secure before version 22.7R2.1 and Ivanti Policy Secure before version 22.7R1.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

A null pointer dereference vulnerability in Ivanti Connect Secure (before 22.7R2.1) and Ivanti Policy Secure (before 22.7R1.1) allows remote unauthenticated attackers to crash the service by triggering the dereference, resulting in denial of service.

MitigationApply the vendor-supplied patches: upgrade Ivanti Connect Secure to version 22.7R2.1 or later, and Ivanti Policy Secure to version 22.7R1.1 or later.

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.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
    Determine whether Ivanti Connect Secure or Ivanti Policy Secure is deployed in your environment. This can be done by checking the product name displayed in the admin web interface or by reviewing your system inventory documentation.
    Affected if Neither product is installed - the CVE does not apply.
  2. Retrieve the installed version of Ivanti Connect Secure
    Log into the admin web interface and navigate to the System Overview page, or check the version via the CLI using the 'show version' command. The version number is typically displayed prominently in the system information section.
    Affected if The installed version is less than 22.7 or equals 22.7 exactly.
  3. Retrieve the installed version of Ivanti Policy Secure
    Log into the admin web interface and navigate to the System Overview page, or check the version via the CLI using the 'show version' command. The version number is typically displayed prominently in the system information section.
    Affected if The installed version is less than 22.7 or equals 22.7 exactly.
  4. Confirm the product is exposed to unauthenticated network access
    Review the network configuration to determine whether the affected service (SSL VPN for Connect Secure, or the authentication portal for Policy Secure) is reachable from unauthenticated network sources. Check firewall rules and access profiles.
    Affected if The service is accessible to unauthenticated remote attackers.

You are affected if either Ivanti Connect Secure version 22.7 or below, or Ivanti Policy Secure version 22.7 or below, is deployed and network-accessible to 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

Apply the vendor-supplied patches: upgrade Ivanti Connect Secure to version 22.7R2.1 or later, and Ivanti Policy Secure to version 22.7R1.1 or later.

Recommended fix High confidence

Connect Secure: 22.7R2.1 or later; Policy Secure: 22.7R1.1 or later

  1. Identify the currently installed version of Ivanti Connect Secure or Ivanti Policy Secure
  2. For Ivanti Connect Secure: upgrade to version 22.7R2.1 or later
  3. For Ivanti Policy Secure: upgrade to version 22.7R1.1 or later
  4. After applying the upgrade, verify the Ivanti service is running properly
  5. Confirm the vulnerability is no longer present by testing normal functionality

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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