IRONSMITHINTEL
HIGHCVSS8.2
|
Actively Exploited
|CISA KEV|CVE-2024-21893|Auth: none — unauthenticated|Reboot: required|Manual only

Ivanti Connect Secure, Policy Secure, and Neurons Server-Side Request Forgery (SSRF) Vulnerability (CVE-2024-21893)

Ivanti Connect Secure (ICS, formerly known as Pulse Connect Secure), Ivanti Policy Secure, and Ivanti Neurons contain a server-side request forgery (SSRF) vulnerability in the SAML component that allows an attacker to access certain restricted resources without authentication.

Published Jan 31, 2024 · Updated May 17, 2026
Why patchRisk explained in plain English
Worst-case scenarioIf unpatched

A remote attacker, without authentication, can achieve full data confidentiality loss, partial data tampering. CISA has confirmed use of this vulnerability in known ransomware campaigns — treat as high priority for remediation. Federal agencies are required to remediate by 2024-02-02 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a Server-Side Request Forgery (SSRF) (CWE-918) vulnerability in Ivanti Connect Secure, Policy Secure, and Neurons. 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. Exploitation requires remote network access, low attack complexity, no authentication required, and no user interaction required.

📧

Phishing link

🖼

Malicious file

🔓

Server compromised

Am I affected?Quick check

Probably yes if any of these apply:

Network Security Team
Firewall Administrators
IT Security
Running connect secure: 9.0, 9.1, 21.9, 21.12, 22.1, 22.2, 22.3, 22.4, 22.6; policy secure: 9.0, 9.1, 22.1, 22.2, 22.3, 22.4, 22.5, 22.6; neurons for zero-trust access: -, 22.2, 22.3, 22.4, 22.5, 22.6
Real-world incidentsWhat we've seen

CISA confirms this CVE has been used in known ransomware campaigns. Added to the KEV catalog on 2024-01-31; federal agencies required to remediate by 2024-02-02.

How to patch

Manual remediation steps

1
Identify affected hosts: query inventory for network-security installs in scope.
2
Apply the vendor security update referenced in CVE-2024-21893's advisory. No specific KB/version is encoded yet — consult the linked MSRC/vendor URL.
3
Verify the fix per the vendor's published verification steps.
4
Document the remediation in your change ticket and re-scan with your vulnerability scanner to confirm closure.
PowerShell automationComing soon

No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.