CVE-2025-0282: Ivanti Connect Secure, Policy Secure, and ZTA Gateways Stack-Based Buffer Overflow
Ivanti Connect Secure, Policy Secure, and ZTA Gateways · listed in the CISA catalog of actively exploited vulnerabilities since 2025-01-08.
- CVSS v3.1 (CVE record)
- 9.0
- critical
- EPSS (exploit probability, 30 days)
- >99.9%
- among the highest 0.1% of all CVEs
- Added to CISA KEV
- 2025-01-08
- US federal due date 2025-01-15
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2025-0282 explained
CVE-2025-0282 is a stack-based buffer overflow in Ivanti Connect Secure, Ivanti Policy Secure and Ivanti Neurons for ZTA gateways. A remote unauthenticated attacker can use it to run code on the device. CISA lists it as known exploited, including in ransomware campaigns, so affected gateways need urgent attention.
Impact
A remote attacker needs no credentials and no user interaction to achieve remote code execution over the network. Attack complexity is high, and CISA rates it as not automatable, so mass exploitation is less straightforward. CISA rates the technical impact as total, meaning full control of the affected gateway. The changed scope means a compromise can affect resources beyond the vulnerable component. Attackers are known to exploit it, including in ransomware attacks.
Who is affected
The CVE record lists Ivanti Connect Secure ≥ 22.7R2, ≤ 22.7R2.4, fixed in 22.7R2.5. Ivanti Neurons for ZTA gateways ≥ 22.7R2, ≤ 22.7R2.3 are affected, with 22.7R2.5 listed as the fixed version. Ivanti Policy Secure ≥ 22.7R1, ≤ 22.7R1.2 is affected, and the CVE record names no fixed version for it. Check the Ivanti advisory for current Policy Secure fix information.
Written with AI from the data on this page and checked against it automatically.
Official 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.
CISA required action: 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.
CISA notes
- CISA Mitigation Instructions: cisa.gov/cisa-mitigation-instructions-CVE-2025-0282 Additional References: forums.ivanti.com/s/article/Security-Advisory-Ivanti-Conn…
- nvd.nist.gov/vuln/detail/CVE-2025-0282
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Ivanti Connect SecureAffectedFixed in
- ≥ 22.7R2, ≤ 22.7R2.4
- 22.7R2.5
- Ivanti Policy SecureAffectedFixed in
- ≥ 22.7R1, ≤ 22.7R1.2
not stated - Ivanti Neurons for ZTA gatewaysAffectedFixed in
- ≥ 22.7R2, ≤ 22.7R2.3
- 22.7R2.5
| Product | Affected | Fixed in |
|---|---|---|
| Ivanti Connect Secure |
|
|
| Ivanti Policy Secure |
| not stated |
| Ivanti Neurons for ZTA gateways |
|
|
How to fix it
- Update to the fixed version for your product:
- Ivanti Connect Secure: 22.7R2.5
- Ivanti Neurons for ZTA gateways: 22.7R2.5
- Vendor advisory: forums.ivanti.com/s/article/Security-Advisory-Ivanti-Conn…
- CISA's deadline for US federal agencies: 2025-01-15 (passed) – a useful benchmark for everyone else, too.
What to do
- Update Ivanti Connect Secure to
22.7R2.5or later. - Update Ivanti Neurons for ZTA gateways to
22.7R2.5or later. - For Ivanti Policy Secure, follow the Ivanti advisory for the fixed release and apply it when available.
- Follow CISA's instructions: conduct hunt activities for signs of compromise and take remediation actions if applicable.
- Apply updates before returning any device to service, as CISA's required action states.
- Limit network exposure of affected gateways where possible and monitor them for unusual activity.
The CVE record names no fixed version for Ivanti Policy Secure. Check the Ivanti advisory for the fixed release and any mitigations. Follow CISA's required action: conduct hunt activities, take remediation actions if applicable, and apply updates before returning a device to service. Restrict network exposure of the device in the meantime.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-121 Stack-based Buffer Overflow
Questions about CVE-2025-0282
- Is CVE-2025-0282 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-01-08 and notes known ransomware use. The US federal due date was 2025-01-15.
- Does an attacker need credentials?
- No. The flaw can be exploited remotely by an unauthenticated attacker without user interaction, although attack complexity is rated high.
- Is patching enough?
- CISA's required action goes further: conduct hunt activities, take remediation actions if applicable, and apply updates before returning a device to service. Follow the CISA instructions and the Ivanti advisory.
Written with AI from the data on this page and checked against it automatically.
References
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.