⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Critical · CVSS 9 ⚠ ACTIVELY EXPLOITED — CISA KEV

How to Fix CVE-2025-0282: Stack Buffer Overflow in Connect Secure

Other vulnerabilities in the same area that are worth patching alongside this one:

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 9 - Critical
Actively exploited?Yes, listed in CISA KEV (added 2025-01-08)
Affected22.7R2 <= 22.7R2.4, 22.7R1 <= 22.7R1.2, 22.7R2 <= 22.7R2.3
Fixed in22.7R2.5, 22.7R2.5
Type (CWE)CWE-121: Stack-based Buffer Overflow
Patch immediately. CISA's KEV listing means active exploitation is confirmed. Federal agencies must remediate by 2025-01-15.

What is CVE-2025-0282?

CVE-2025-0282 is a stack-based buffer overflow in Connect Secure. A remote attacker can send a crafted message that overflows a fixed-size stack buffer, corrupting the return address and, on un-mitigated builds, achieving code execution. Vendor description: 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.

Why this CVE matters

Stack-based buffer overflows in network-reachable services have driven some of the highest-impact incidents of the past two years. Modern compiler protections raise the bar, but real-world exploits for unpatched appliances continue to appear quickly after disclosure.

For deployments of Connect Secure that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Confirmed in-the-wild exploitation makes that assumption mandatory, not cautious. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

Open the Ivanti product's About page in the admin UI or run the documented version-check command from the vendor's release notes. Cross-reference the build number against the advisory.

How to fix CVE-2025-0282

  1. Read the vendor advisory in full: https://forums.ivanti.com/s/article/Security-Advisory-Ivanti-Connect-Secure-Policy-Secure-ZTA-Gateways-CVE-2025-0282-CVE-2025-0283
  2. Upgrade Connect Secure to 22.7R2.5, 22.7R2.5 or a later version listed in the vendor advisory.
  3. Back up the configuration (and database, where applicable) before upgrading.
  4. Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
  5. Restart the affected service so the patched binary loads, then verify the new version (see verification section).

Upgrade the Ivanti / pulse secure appliance


# Web admin: System -> Upgrade/Downgrade -> stage the patched image
# referenced in the advisory: https://forums.ivanti.com/s/article/Security-Advisory-Ivanti-Connect-Secure-Policy-Secure-ZTA-Gateways-CVE-2025-0282-CVE-2025-0283

# CLI verification after reboot
show version
show system status

Verify the fix landed


# 1. Confirm the running version matches the fixed-in version from the advisory:
#    https://forums.ivanti.com/s/article/Security-Advisory-Ivanti-Connect-Secure-Policy-Secure-ZTA-Gateways-CVE-2025-0282-CVE-2025-0283
#    Use the platform-specific version probe above.

# 2. Re-scan with your vulnerability scanner (Nessus, Qualys, Tenable, OpenVAS).
#    The scanner should no longer flag CVE-2025-0282 on the patched target.

# 3. Inspect recent service / kernel logs for crash loops or rollback events.
journalctl -u <service> --since "10 minutes ago"
dmesg --since "10 minutes ago"

If you cannot patch immediately

Block network reachability to the vulnerable service from untrusted networks and apply the patched build. Memory-corruption bugs cannot be reliably mitigated at the network layer; the patch is the fix.

How to verify the fix worked

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for repeated service restarts, crash logs from the affected daemon, and core files generated around the time of any anomalous traffic. A memory-corruption flaw used for exploitation often leaves a trail of failed attempts before the successful one. Because Connect Secure sits on CISA's Known Exploited Vulnerabilities catalog for this CVE, defenders should also pull the IOC list from the vendor advisory and from CISA's analysis if one was published.

Frequently asked questions

Is CVE-2025-0282 being exploited in the wild?

Yes. CISA added CVE-2025-0282 to the Known Exploited Vulnerabilities catalog, which means active exploitation has been confirmed by federal observation or credible vendor reporting.

Will a WAF or IDS rule fully mitigate CVE-2025-0282?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for Connect Secure run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

References

*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*