dbcve.org
Connect SecureApplication · Ivanti

CVE-2025-5456

HIGH · 7.5 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 22.7 / 22.8 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 buffer over-read vulnerability in Ivanti Connect Secure before 22.7R2.8 or 22.8R2, Ivanti Policy Secure before 22.7R1.5, Ivanti ZTA Gateway before 2.8R2.3-723 and Ivanti Neurons for Secure Access before 22.8R1.4 (Fix deployed on 02-Aug-2025) allows a remote unauthenticated attacker to trigger a denial of service. CWE-125

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 buffer over-read vulnerability (CWE-125) exists in multiple Ivanti products including Connect Secure, Policy Secure, ZTA Gateway, and Neurons for Secure Access. The flaw allows a remote unauthenticated attacker to read memory beyond buffer boundaries, leading to denial of service. Affected versions span specific releases prior to 22.7R2.8/22.8R2 for Connect Secure, 22.7R1.5 for Policy Secure, 2.8R2.3-723 for ZTA Gateway, and 22.8R1.4 for Neurons.

MitigationApply the vendor-supplied patches (deployed 02-Aug-2025) by upgrading to the fixed version numbers for each affected product. Schedule during maintenance window as upgrade will require brief service interruption.

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
Zero Trust Access GatewayApplication
Affected:= 22.8
Neurons For Secure AccessApplication
Affected:< 22.8= 22.8

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 Ivanti product installed
    Access the admin console or check system information to determine which Ivanti product is running: Connect Secure, Policy Secure, Zero Trust Access Gateway, or Neurons for Secure Access
    Affected if The product is one of these four and the version matches the affected ranges
  2. Check the installed version number
    Log into the admin interface and navigate to the System > Status or Help > About page to view the exact software version, or use the command line: 'show version' or 'dp get system version'
    Affected if Version is < 22.7 or = 22.7 for Connect Secure or Policy Secure; = 22.8 for Zero Trust Access Gateway; < 22.8 or = 22.8 for Neurons for Secure Access
  3. Confirm the SSL VPN or web portal is accessible
    Attempt to access the login page via HTTPS at the external URL or internal hostname (e.g., https://your-gateway.hostname)
    Affected if The web interface is reachable, as the vulnerability allows remote unauthenticated attackers to trigger the buffer over-read
  4. Check for recent security updates
    Review the System > Maintenance > Software Updates or Check Point/Security Advisory logs to see if patch 22.7R2.8, 22.8R2, or the corresponding fixes for other products have been applied
    Affected if No security patches have been installed since August 2025, or the version remains in the affected range

You are affected if any of these Ivanti products (Connect Secure, Policy Secure, ZTA Gateway, or Neurons for Secure Access) are running a version that matches: < 22.7, = 22.7, or = 22.8 (depending on the product), and the web interface is exposed.

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 / 22.8 or later
Fixed in 22.722.8
Interim mitigation

Apply the vendor-supplied patches (deployed 02-Aug-2025) by upgrading to the fixed version numbers for each affected product. Schedule during maintenance window as upgrade will require brief service interruption.

Recommended fix High confidence

Connect Secure: 22.7R2.8 or 22.8R2; Policy Secure: 22.7R1.5; ZTA Gateway: 2.8R2.3-723; Neurons for Secure Access: 22.8R1.4

  1. 1. Identify the exact Ivanti product and current version running in your environment (Connect Secure, Policy Secure, ZTA Gateway, or Neurons for Secure Access).
  2. 2. Consult the official Ivanti release notes or support portal to obtain the specific upgrade package for your product.
  3. 3. For Connect Secure: upgrade to version 22.7R2.8 or 22.8R2 or later.
  4. 4. For Policy Secure: upgrade to version 22.7R1.5 or later.
  5. 5. For ZTA Gateway: upgrade to version 2.8R2.3-723 or later.
  6. 6. For Neurons for Secure Access: upgrade to version 22.8R1.4 or later.
  7. 7. After upgrade, verify the new version is running and test critical functionality to ensure the upgrade was successful.

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

Fix this in Connect Secure Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
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,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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