dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 15 Jan 2025. Known ransomware use
Connect SecureApplication · Ivanti

CVE-2025-0282

CRITICAL · 9.0 CVSS v3.1 Published 2025-01-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Public exploit 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 stack-based buffer overflow in Ivanti Connect Secure before version 22.7R2.5, Ivanti Policy Secure before version 22.7R1.2, and Ivanti Neurons for ZTA gateways before version 22.7R2.3 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 confidence

A stack-based buffer overflow vulnerability in Ivanti Connect Secure, Policy Secure, and Neurons for ZTA gateways allows remote unauthenticated attackers to execute arbitrary code on affected systems by overflowing a stack buffer.

MitigationUpgrade Ivanti Connect Secure to version 22.7R2.5 or later, Policy Secure to 22.7R1.2 or later, and Neurons for ZTA gateways to 22.7R2.3 or later to remediate this vulnerability.

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
Neurons For Zero Trust AccessApplication
Affected:= 22.7
Policy SecureApplication
Affected:= 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
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Ivanti product installed
    Access the device admin interface or check system information to determine if the device is running Ivanti Connect Secure, Policy Secure, or Neurons for Zero Trust Access
    Affected if The device runs any of these three products
  2. Determine the installed version number
    Log into the admin console and navigate to System > Administration > System Information, or run 'show version' via CLI to retrieve the exact firmware version
    Affected if The version displays as 22.7.x (any minor version)
  3. Compare version against patched releases
    Compare your installed version against: Connect Secure patched at 22.7R2.5 or higher, Policy Secure patched at 22.7R1.2 or higher, Neurons for ZTA patched at 22.7R2.3 or higher
    Affected if The installed version is lower than the respective patched release for your product (22.7R2.5 for Connect Secure, 22.7R1.2 for Policy Secure, 22.7R2.3 for Neurons)
  4. Verify device is network accessible
    Confirm the Ivanti admin or SSL VPN web interface is reachable from network, as this is a remote unauthenticated vulnerability
    Affected if The management or VPN web interface is exposed to network (especially untrusted networks)

A user is affected if their device runs any Ivanti Connect Secure, Policy Secure, or Neurons for ZTA on version 22.7.x prior to the product-specific patched release and the interface is network-accessible.

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

Upgrade Ivanti Connect Secure to version 22.7R2.5 or later, Policy Secure to 22.7R1.2 or later, and Neurons for ZTA gateways to 22.7R2.3 or later to remediate this vulnerability.

Recommended fix High confidence

Connect Secure: 22.7R2.5+ | Policy Secure: 22.7R1.2+ | Neurons for ZTA: 22.7R2.3+

  1. Identify the affected Ivanti product (Connect Secure, Policy Secure, or Neurons for ZTA)
  2. Determine the current installed version by checking the device management interface or system information
  3. For Ivanti Connect Secure: Upgrade to version 22.7R2.5 or later
  4. For Ivanti Policy Secure: Upgrade to version 22.7R1.2 or later
  5. For Ivanti Neurons for ZTA: Upgrade to version 22.7R2.3 or later
  6. Download the appropriate update from the official Ivanti support portal
  7. Review Ivanti release notes for any specific upgrade prerequisites or procedures
  8. Perform the upgrade following Ivanti's documented upgrade process

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

Fix this in Connect Secure Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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