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
This vulnerability carries a CRITICAL severity rating with a CVSS v3.1 score of 9.8, indicating it can be exploited remotely over the network with relatively low complexity without requiring user interaction and does not require pre-existing privileges . The vulnerability impacts confidentiality (data exposure), integrity (unauthorized modifications), and availability (service disruption) for affected systems. Impacting 2 products from ivanti, from ivanti organizations running these solutions should prioritize assessment and patching.
Reported in 2024, this vulnerability emerged during an era marked by increased sophistication in supply chain attacks, cloud infrastructure vulnerabilities, and software-as-a-service (SaaS) security challenges. Security practices during this period emphasized zero-trust architectures, container security, and API protection.
2024-04-04T23:15:15.640
2024-11-21T08:55:12.850
Modified
CVSSv3.1: 9.8 (CRITICAL)
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | ivanti | connect_secure | 9.1 | Yes |
| Application | ivanti | connect_secure | 9.1 | Yes |
| Application | ivanti | connect_secure | 9.1 | Yes |
| Application | ivanti | connect_secure | 9.1 | Yes |
| Application | ivanti | connect_secure | 9.1 | Yes |
| Application | ivanti | connect_secure | 9.1 | Yes |
| Application | ivanti | connect_secure | 9.1 | Yes |
| Application | ivanti | connect_secure | 9.1 | Yes |
| Application | ivanti | connect_secure | 9.1 | Yes |
| Application | ivanti | connect_secure | 9.1 | Yes |
| Application | ivanti | connect_secure | 9.1 | Yes |
| Application | ivanti | connect_secure | 9.1 | Yes |
| Application | ivanti | connect_secure | 9.1 | Yes |
| Application | ivanti | connect_secure | 9.1 | Yes |
| Application | ivanti | connect_secure | 9.1 | Yes |
| Application | ivanti | connect_secure | 9.1 | Yes |
| Application | ivanti | connect_secure | 9.1 | Yes |
| Application | ivanti | connect_secure | 9.1 | Yes |
| Application | ivanti | connect_secure | 9.1 | Yes |
| Application | ivanti | connect_secure | 9.1 | Yes |
| Application | ivanti | connect_secure | 9.1 | Yes |
| Application | ivanti | connect_secure | 9.1 | Yes |
| Application | ivanti | connect_secure | 22.1 | Yes |
| Application | ivanti | connect_secure | 22.2 | Yes |
| Application | ivanti | connect_secure | 22.3 | Yes |
| Application | ivanti | connect_secure | 22.4 | Yes |
| Application | ivanti | connect_secure | 22.5 | Yes |
| Application | ivanti | connect_secure | 22.6 | Yes |
| Application | ivanti | policy_secure | 9.0 | Yes |
| Application | ivanti | policy_secure | 9.0 | Yes |
| Application | ivanti | policy_secure | 9.0 | Yes |
| Application | ivanti | policy_secure | 9.0 | Yes |
| Application | ivanti | policy_secure | 9.0 | Yes |
| Application | ivanti | policy_secure | 9.0 | Yes |
| Application | ivanti | policy_secure | 9.0 | Yes |
| Application | ivanti | policy_secure | 9.1 | Yes |
| Application | ivanti | policy_secure | 9.1 | Yes |
| Application | ivanti | policy_secure | 9.1 | Yes |
| Application | ivanti | policy_secure | 9.1 | Yes |
| Application | ivanti | policy_secure | 9.1 | Yes |
| Application | ivanti | policy_secure | 9.1 | Yes |
| Application | ivanti | policy_secure | 9.1 | Yes |
| Application | ivanti | policy_secure | 9.1 | Yes |
| Application | ivanti | policy_secure | 9.1 | Yes |
| Application | ivanti | policy_secure | 9.1 | Yes |
| Application | ivanti | policy_secure | 9.1 | Yes |
| Application | ivanti | policy_secure | 9.1 | Yes |
| Application | ivanti | policy_secure | 9.1 | Yes |
| Application | ivanti | policy_secure | 9.1 | Yes |
| Application | ivanti | policy_secure | 9.1 | Yes |
| Application | ivanti | policy_secure | 9.1 | Yes |
| Application | ivanti | policy_secure | 9.1 | Yes |
| Application | ivanti | policy_secure | 9.1 | Yes |
| Application | ivanti | policy_secure | 9.1 | Yes |
| Application | ivanti | policy_secure | 22.1 | Yes |
| Application | ivanti | policy_secure | 22.2 | Yes |
| Application | ivanti | policy_secure | 22.3 | Yes |
| Application | ivanti | policy_secure | 22.4 | Yes |
| Application | ivanti | policy_secure | 22.5 | Yes |
| Application | ivanti | policy_secure | 22.6 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For ivanti's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.