Connect Secure: Out-of-bounds Write
CVE-2024-21894 is a critical-severity out-of-bounds write vulnerability in Connect Secure from Ivanti, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 22.1R6.2, 22.2R4.2, 22.3R1.2 as the first without the flaw, so updating Connect Secure to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 19% chance of exploitation within 30 days, which is in the top 2.65% of all scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Connect Secure to 22.1R6.2 or 22.2R4.2 or 22.3R1.2 or 22.4R1.2, whichever matches your release line, or a later version.
- Update Policy Secure to 22.4R1.2 or 22.6R1.2 or 9.1R16.4 or 9.1R17.4, whichever matches your release line, or a later version.
- 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.1R6.2 up to, but not including, 22.1R6.2; 22.2R4.2 up to, but not including, 22.2R4.2; 22.3R1.2 up to, but not including, 22.3R1.2; 22.4R1.2 up to, but not including, 22.4R1.2; 22.4R2.4 up to, but not including, 22.4R2.4; 22.5R1.3 up to, but not including, 22.5R1.3; 22.5R2.4 up to, but not including, 22.5R2.4; 22.6R2.3 up to, but not including, 22.6R2.3; and 18 more ranges | 22.1R6.2, 22.2R4.2, 22.3R1.2, 22.4R1.2, 22.4R2.4, 22.5R1.3 |
| Ivanti | Policy Secure | 22.4R1.2 up to, but not including, 22.4R1.2; 22.6R1.2 up to, but not including, 22.6R1.2; 9.1R16.4 up to, but not including, 9.1R16.4; 9.1R17.4 up to, but not including, 9.1R17.4; 9.1R18.5 up to, but not including, 9.1R18.5; 22.4R1.2; 22.6R1.2; 9.1R16.4; and 2 more ranges | 22.4R1.2, 22.6R1.2, 9.1R16.4, 9.1R17.4, 9.1R18.5 |
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
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- 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:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.8 | Critical | NVD |
| CVSS 3.0 | 8.2 | High | CNA (hackerone.com) |
Official description
A heap overflow vulnerability in IPSec component of Ivanti Connect Secure (9.x, 22.x) and Ivanti Policy Secure allows an unauthenticated malicious user to send specially crafted requests in-order-to crash the service thereby causing a DoS attack. In certain conditions this may lead to execution of arbitrary code
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.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
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
- 8.2 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.