First published: Thu Apr 04 2024(Updated: )
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 or in certain conditions read contents from memory.
Credit: support@hackerone.com
Affected Software | Affected Version | How to fix |
---|---|---|
Ivanti Connect Secure (ICS) VPN | =9.1-r1 | |
Ivanti Connect Secure (ICS) VPN | =9.1-r10 | |
Ivanti Connect Secure (ICS) VPN | =9.1-r11 | |
Ivanti Connect Secure (ICS) VPN | =9.1-r11.5 | |
Ivanti Connect Secure (ICS) VPN | =9.1-r12 | |
Ivanti Connect Secure (ICS) VPN | =9.1-r13 | |
Ivanti Connect Secure (ICS) VPN | =9.1-r14 | |
Ivanti Connect Secure (ICS) VPN | =9.1-r15 | |
Ivanti Connect Secure (ICS) VPN | =9.1-r16 | |
Ivanti Connect Secure (ICS) VPN | =9.1-r17 | |
Ivanti Connect Secure (ICS) VPN | =9.1-r18 | |
Ivanti Connect Secure (ICS) VPN | =9.1-r2 | |
Ivanti Connect Secure (ICS) VPN | =9.1-r3 | |
Ivanti Connect Secure (ICS) VPN | =9.1-r4 | |
Ivanti Connect Secure (ICS) VPN | =9.1-r4.1 | |
Ivanti Connect Secure (ICS) VPN | =9.1-r4.2 | |
Ivanti Connect Secure (ICS) VPN | =9.1-r4.3 | |
Ivanti Connect Secure (ICS) VPN | =9.1-r5 | |
Ivanti Connect Secure (ICS) VPN | =9.1-r6 | |
Ivanti Connect Secure (ICS) VPN | =9.1-r7 | |
Ivanti Connect Secure (ICS) VPN | =9.1-r8 | |
Ivanti Connect Secure (ICS) VPN | =9.1-r9 | |
Ivanti Connect Secure (ICS) VPN | =22.1 | |
Ivanti Connect Secure (ICS) VPN | =22.2 | |
Ivanti Connect Secure (ICS) VPN | =22.3 | |
Ivanti Connect Secure (ICS) VPN | =22.4 | |
Ivanti Connect Secure (ICS) VPN | =22.5 | |
Ivanti Connect Secure (ICS) VPN | =22.6 | |
Pulse Policy Secure | =9.0 | |
Pulse Policy Secure | =9.0-r1 | |
Pulse Policy Secure | =9.0-r2 | |
Pulse Policy Secure | =9.0-r2.1 | |
Pulse Policy Secure | =9.0-r3 | |
Pulse Policy Secure | =9.0-r3.1 | |
Pulse Policy Secure | =9.0-r4 | |
Pulse Policy Secure | =9.1 | |
Pulse Policy Secure | =9.1-r1 | |
Pulse Policy Secure | =9.1-r10 | |
Pulse Policy Secure | =9.1-r11 | |
Pulse Policy Secure | =9.1-r12 | |
Pulse Policy Secure | =9.1-r13 | |
Pulse Policy Secure | =9.1-r14 | |
Pulse Policy Secure | =9.1-r15 | |
Pulse Policy Secure | =9.1-r16 | |
Pulse Policy Secure | =9.1-r17 | |
Pulse Policy Secure | =9.1-r18 | |
Pulse Policy Secure | =9.1-r2 | |
Pulse Policy Secure | =9.1-r3 | |
Pulse Policy Secure | =9.1-r4 | |
Pulse Policy Secure | =9.1-r5 | |
Pulse Policy Secure | =9.1-r6 | |
Pulse Policy Secure | =9.1-r7 | |
Pulse Policy Secure | =9.1-r8 | |
Pulse Policy Secure | =9.1-r9 | |
Pulse Policy Secure | =22.1 | |
Pulse Policy Secure | =22.2 | |
Pulse Policy Secure | =22.3 | |
Pulse Policy Secure | =22.4 | |
Pulse Policy Secure | =22.5 | |
Pulse Policy Secure | =22.6 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-22053 is considered a critical severity vulnerability due to its potential to cause a denial-of-service (DoS) and allow unauthorized memory access.
To fix CVE-2024-22053, you should update your Ivanti Connect Secure and Ivanti Policy Secure software to the latest patched versions provided by Ivanti.
CVE-2024-22053 affects various versions of Ivanti Connect Secure and Ivanti Policy Secure from 9.x and 22.x series.
The impact of CVE-2024-22053 includes potential service crashes and unauthorized access to sensitive memory contents.
You are vulnerable to CVE-2024-22053 if you are running affected versions of Ivanti Connect Secure or Ivanti Policy Secure listed in the vulnerability report.