CVE-2025-22457
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 stack-based buffer overflow in Ivanti Connect Secure before version 22.7R2.6, Ivanti Policy Secure before version 22.7R1.4, and Ivanti ZTA Gateways before version 22.8R2.2 allows a remote unauthenticated attacker to achieve remote code execution.
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 stack-based buffer overflow vulnerability in Ivanti Connect Secure, Policy Secure, and ZTA Gateways allows remote unauthenticated attackers to achieve remote code execution. The vulnerability exists in versions prior to 22.7R2.6 (Connect Secure), 22.7R1.4 (Policy Secure), and 22.8R2.2 (ZTA Gateways).
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< 22.7= 22.7< 22.7= 22.7< 22.8= 22.8CVSS 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 productDetermine which Ivanti product is deployed: Connect Secure, Policy Secure, or Zero Trust Access Gateway. This can typically be found in the product UI, system information page, or by checking the product name in the administration console.Affected if The system is running any of these three products.
-
Check the installed version of Ivanti Connect SecureIn the admin console, navigate to System > Administration > System Overview, or check the login page footer which often displays the version. The version is typically shown as a numeric release such as 22.x.Affected if The installed version is 22.7 or any version lower than 22.7.
-
Check the installed version of Ivanti Policy SecureIn the admin console, navigate to System > Administration > System Overview, or check the login page footer which often displays the version. The version is typically shown as a numeric release such as 22.x.Affected if The installed version is 22.7 or any version lower than 22.7.
-
Check the installed version of Ivanti Zero Trust Access GatewayIn the admin console, navigate to System > Administration > System Overview, or check the login page footer which often displays the version. The version is typically shown as a numeric release such as 22.x.Affected if The installed version is 22.8 or any version lower than 22.8.
-
Verify if the VPN/gateway interface is network-accessibleConfirm whether the Ivanti Connect Secure, Policy Secure, or ZTA Gateway admin interface or VPN portal is reachable from untrusted networks. This can be checked via network scans, firewall rules, or by attempting to access the login page from an external IP.Affected if The interface is exposed to the internet or untrusted networks, making it exploitable by remote unauthenticated attackers.
You are affected if you are running Ivanti Connect Secure or Policy Secure at version 22.7 or below, or Ivanti Zero Trust Access Gateway at version 22.8 or below, and the gateway interface is network-accessible.
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.
dbcve · scoped22.722.8
Upgrade Ivanti Connect Secure to version 22.7R2.6 or later, Ivanti Policy Secure to 22.7R1.4 or later, and Ivanti ZTA Gateways to 22.8R2.2 or later to remediate this vulnerability.
Connect Secure: 22.7R2.6+ | Policy Secure: 22.7R1.4+ | ZTA Gateways: 22.8R2.2+
- 1. Identify the affected Ivanti product (Connect Secure, Policy Secure, or Zero Trust Access Gateway) currently deployed
- 2. Determine the current installed version of the product
- 3. For Connect Secure: Upgrade to version 22.7R2.6 or later
- 4. For Policy Secure: Upgrade to version 22.7R1.4 or later
- 5. For Zero Trust Access Gateway: Upgrade to version 22.8R2.2 or later
- 6. After upgrade, verify the new version is correctly installed
- 7. Test critical VPN and authentication functionality to ensure normal operations
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22457 — 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-2025-22457 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