CVE REMEDIATION GUIDE
CISA KEV · Known exploitedCriticalResearch in progress

CVE-2025-0282 remediation guide

Ivanti Connect Secure, Policy Secure, Neurons for ZTA gateways

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.

Open CVE record
Research in progress

A verified fixed-version field is not available. Use the linked NVD and supporting references, then confirm the vendor-supported path before changing production systems.

ProductIvanti Connect Secure, Policy Secure, Neurons for ZTA gateways
Affected versions>= 22.7R2 <= 22.7R2.4, >= 22.7R1 <= 22.7R1.2, >= 22.7R2 <= 22.7R2.3, 22.7
Fixed versionsNo verified fixed-version field is available yet
Priority basisImmediate · CVSS 9 · EPSS 100.0%
01

Identify the affected asset

Confirm whether Ivanti Connect Secure, Policy Secure, Neurons for ZTA gateways is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= 22.7R2 <= 22.7R2.4, >= 22.7R1 <= 22.7R1.2, >= 22.7R2 <= 22.7R2.3, 22.7. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Apply mitigations as set forth in the CISA instructions linked below to include conducting hunt activities, taking remediation actions if applicable, and applying updates prior to returning a device to service.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.