Ivanti Connect Secure, Policy Secure, and ZTA Gateways Stack-Based Buffer Overflow
CVE-2025-0282 is a critical-severity out-of-bounds write vulnerability in Connect Secure from Ivanti, with a CVSS 3.1 base score of 9.0 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected Connect Secure versions: 22.7R2 through 22.7R2.4. The record does not name a fixed version, so check the vendor advisory. CISA added it to the Known Exploited Vulnerabilities catalogue on January 8, 2025, which means attacks have been observed in the wild, including in ransomware campaigns.
Attackers are already exploiting this vulnerability, according to CISA.
What to do
- Check which version of Connect Secure you run against the affected versions below, and install the vendor's latest release.
- CISA's 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.
- Read the advisory on forums.ivanti.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Ivanti | Connect Secure | 22.7R2 through 22.7R2.4 | Not stated |
| Ivanti | Policy Secure | 22.7R1 through 22.7R1.2 | Not stated |
| Ivanti | Neurons for ZTA gateways | 22.7R2 through 22.7R2.3 | Not stated |
| Ivanti | Neurons For Zero-trust Access | 22.7 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.0 | Critical | CNA |
| CVSS 3.1 | 9.0 | Critical | NVD |
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Out-of-bounds Write
The product writes data past the end, or before the beginning, of the intended buffer.
How developers prevent this class of flaw
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
Timeline
- CVE record published.
- Added to CISA's Known Exploited Vulnerabilities catalogue.
- Deadline for US federal agencies to remediate, set by CISA.
- CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- cisa.gov/cisa-mitigation-instructions-cve-2025-0282Third Party Advisory, US Government Resource
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-0282US Government Resource
- cisa.gov/known-exploited-vulnerabilities-catalog?search_api_fulltext=CVE-2025-0282US Government Resource
Technical write-ups (may include proof of concept)
- cloud.google.com/blog/topics/threat-intelligence/ivanti-connect-secure-vpn-zero-dayExploit, Technical Description
- github.com/sfewer-r7/CVE-2025-0282Exploit
- labs.watchtowr.com/exploitation-walkthrough-and-techniques-ivanti-connect-secure-rce-cve-2025-0282/Exploit, Third Party Advisory
Other vulnerabilities in Connect Secure
- 4.3 Medium severity
- 7.0 High severity
- 8.6 High severity
- 7.6 High severity
- 8.8 High severity
- 8.9 High severity
Recent Out-of-bounds Write vulnerabilities
- 7.0 High severity
- 7.8 High severity
- 9.8 Critical severity
- 7.5 High severity
- 8.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.