Cyber Resilience

CVE-2024-21893

SSRF in Ivanti Connect Secure 21.12 … 9.1

CISA KEVActive ExploitationEUVD ExploitedRansomware-linkedSSRF
Published
31 January 2024
Modified
04 August 2026
KEV Added
31 January 2024
Patch / advisory
CVSS Score v3.1 8.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
EPSS Score 0.99 100.0th percentile
Risk Priority 87 floored blend · peak EPSS

Summary

CVE-2024-21893 is a high-severity SSRF (CWE-918) vulnerability in Ivanti Connect Secure. Its CVSS base score is 8.2 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 0.0% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.

The strongest mitigations our analysis identified map to AC-4 (Information Flow Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2024-21893 is a server-side request forgery vulnerability (CWE-918) residing in the SAML component of Ivanti Connect Secure versions 9.x and 22.x, Ivanti Policy Secure versions 9.x and 22.x, and Ivanti Neurons for ZTA. The flaw carries a CVSS 3.1 score of 8.2 and permits an unauthenticated attacker to reach restricted resources that should otherwise be inaccessible.

An attacker can exploit the issue over the network without credentials or user interaction to issue crafted requests from the affected server, resulting in high-impact confidentiality exposure combined with limited integrity effects. Because the vulnerability requires no authentication, remote adversaries, including automated scanners and threat actors, can target exposed Ivanti appliances directly.

Ivanti security advisories referenced in the supplied links address related issues in the same product families and direct customers to apply vendor-supplied patches. The CVE is also catalogued in CISA’s Known Exploited Vulnerabilities list, confirming that mitigation through updates or compensating controls is required for affected deployments.

The associated EPSS score has reached a peak of 0.9640 with a current value of 0.9432, indicating sustained and widespread exploitation interest following disclosure.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A server-side request forgery vulnerability in the SAML component of Ivanti Connect Secure (9.x, 22.x) and Ivanti Policy Secure (9.x, 22.x) and Ivanti Neurons for ZTA allows an attacker to access certain restricted resources without authentication.

CWE(s)
KEV Date Added
31 January 2024

Related Threats

Threat-Actor AttributionAI

UNC5221 (G0125)aka Silk Typhoon
Mandiant and Microsoft attributed mass exploitation of the 2024 Ivanti Connect Secure zero-day chain (incl. CVE-2024-21893 SSRF) to UNC5221 / Silk Typhoon espionage operations.

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-0292Same product: Ivanti Connect Secure
CVE-2025-0282Same product: Ivanti Connect Secureboth on KEV
CVE-2025-55139Same product: Ivanti Connect Secure
CVE-2019-11510Same product: Ivanti Connect Secureboth on KEV
CVE-2023-46805Same product: Ivanti Connect Secureboth on KEV
CVE-2024-21887Same product: Ivanti Connect Secureboth on KEV
CVE-2020-8243Same product: Ivanti Connect Secureboth on KEV
CVE-2025-5450Same product: Ivanti Connect Secure
CVE-2025-0283Same product: Ivanti Connect Secure
CVE-2025-22457Same product: Ivanti Connect Secureboth on KEV

Affected Assets

ivanti
connect secure
21.12, 21.9, 22.1, 22.2, 22.3
ivanti
policy secure
22.1, 22.2, 22.3, 22.4, 22.5
ivanti
neurons for zero-trust access
22.2, 22.3, 22.4, 22.5, 22.6

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.3.6
  • V1.5.3
  • V5.3.2
  • V10.4.7

Mitigating Controls (NIST 800-53 r5) AI

Information flow enforcement can restrict which destinations the server is allowed to contact on behalf of users.

Input validation directly stops untrusted URLs from being accepted and fetched without destination checks.

Boundary protection limits the network reach of server-initiated requests even if SSRF occurs.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure development practices directly include input validation and destination allow-listing that prevent SSRF.

DE.CM-09 partial match
prevents

Runtime monitoring of web applications and services can detect anomalous outbound requests indicative of SSRF.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover and record SSRF flaws in web applications.

PR.IR-01 partial match
prevents

Network segmentation and egress controls can limit the damage from successful SSRF requests.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Operational threat data describing SSRF campaigns can be used to tighten outbound-request allow-lists and detection rules before attackers exploit them.

References