Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2024-21893: Unauthenticated SAML SSRF in Ivanti Connect Secure, Policy Secure, and Neurons for ZTA

Published Jan 31, 2024 · Updated 15 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS8.2High · v3.1
EPSS100.0%100th percentile
CISA KEVYesAdded Jan 31, 2024
In the wildActivePer CISA KEV
Vendor
Ivanti
IdentifiersCVE-2024-21893CWE-918 · Server-Side Request Forgery (SSRF)

CVE-2024-21893 is a server-side request forgery vulnerability in the SAML component of Ivanti Connect Secure and Ivanti Policy Secure releases in the 9.x and 22.x families, and Ivanti Neurons for ZTA gateways. Crafted SAML requests can cause an affected appliance to access restricted backend resources without authentication. Observed exploitation used malicious SOAP/XML input to reach a locally bound backend API where frontend authentication checks did not apply. Attackers can chain this access with command injection vulnerability CVE-2024-21887 to execute arbitrary commands without authentication, including on appliances protected by the original January 2024 mitigation. The vulnerability has been exploited in the wild and is included in CISA's Known Exploited Vulnerabilities catalog.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation permits unauthenticated access to certain restricted resources, with potential disclosure of sensitive information and limited integrity impact. Ivanti assigned a CVSS score of 8.2. When chained with CVE-2024-21887, the vulnerability enables arbitrary command execution and appliance compromise. Observed campaigns involving this chain included malware deployment, privileged credential collection, and lateral movement into internal networks. Arbitrary command execution is a consequence of the exploit chain, not an independently established capability of the SSRF flaw alone.

Mitigation

If you can’t patch tonight, do this now.

If patching must be delayed, apply Ivanti's updated interim mitigation for CVE-2024-21893 rather than relying on the original January 10, 2024 mitigation, which the SSRF exploit chain can bypass. Disconnect or isolate affected gateways from enterprise resources where feasible. Monitor authentication, account usage, identity services, unexpected network services, and outbound connections, and hunt for compromise on connected systems. Use the applicable updated external integrity checker alongside continuous security monitoring; a clean integrity result does not exclude historical compromise or attacker evasion. Temporary mitigation is not a substitute for patching and compromise assessment.

Remediation

Patch, then assume compromise.

Upgrade affected deployments to the latest vendor-supported patched release for the applicable product and release branch. Ivanti's February 8 and February 14, 2024 updates superseded the January 31 and February 1 patches; do not rely on those initial builds as the final remediation baseline. Follow Ivanti's recovery guidance to address possible persistence: factory-reset physical appliances before patching, or rebuild virtual appliances using a clean image, restore the configuration, and revoke or rotate device credentials. Appliances already successfully reset and patched under the earlier procedure did not require another reset solely to install the superseding patches. Investigate potential pre-patch compromise and continue threat hunting after upgrading.

Public exploits

Exploits

4 exploits validated by Mallory's analysis.

View more in app →
ivanti_connect_secure_rce_cve_2024_21893.rbThis repository contains a single Metasploit module exploit targeting Ivanti Connect Secure and Ivanti Policy Secure appliances vulnerable to a chained SSRF (CVE-2024-21893) and command injection (CVE-2024-21887) attack. The exploit works by sending a crafted SOAP request to the public '/dana-ws/saml20.ws' endpoint, which leverages the SSRF to access an internal backend service on 127.0.0.1:8090. This backend is then exploited via command injection, allowing arbitrary command execution as root. The module supports a variety of Metasploit payloads, including reverse shells and Meterpreter sessions. The check method attempts to fingerprint the target by requesting '/dana-na/css/visibility.css' and looking for a 'Pulse Secure' banner. The exploit is weaponized, unauthenticated, and provides full remote code execution on affected systems. The code is written in Ruby and is structured as a standard Metasploit module.Disclosed Jan 31, 2024 · Framework: metasploit · ruby · networkWeaponizedCVE-2024-21893-to-CVE-2024-21887This repository provides a working exploit for chaining two critical vulnerabilities in Ivanti Connect Secure and Policy Secure appliances: CVE-2024-21893 (SSRF) and CVE-2024-21887 (command injection). The main exploit script (exploit.py) is written in Python and automates the attack by sending a crafted XML payload to the vulnerable endpoint (/dana-ws/saml20.ws) on the target. The payload leverages SSRF to reach an internal service and injects a command that opens a reverse shell to the attacker's machine. The script can also set up a listener using pwncat to handle the incoming shell. Two Nuclei YAML templates are included for detection of the SSRF and the SSRF-to-RCE chain, targeting the same endpoint. The repository is structured with a README.md (usage and background), the main exploit script, two detection templates, and a requirements.txt for dependencies. The exploit is operational and provides unauthenticated remote code execution if the target is vulnerable and unpatched.Chocapikk · Disclosed Feb 3, 2024 · python · yaml · networkOperationalabyss-c2This repository is a multi-module Python offensive framework centered on exploiting HiSilicon DVR/NVR/IP camera devices via CVE-2020-25078, then managing compromised hosts through a Flask/SocketIO web panel. It is not a simple single-file PoC: it includes a control server (server.py), persistence and post-exploitation tooling, credential attacks, recon modules, web vulnerability scanners, network service checks, pivoting, reverse shell support, and a SQLite-backed datastore. Core exploit logic is in exploit.py and scanner.py. exploit.py probes numerous traversal/disclosure paths such as /../../.../mnt/mtd/Config/Account1 and related config/system files, parses returned content with multiple regex patterns to recover credentials, fingerprints device families, and falls back to known default credentials when disclosure succeeds but parsing does not. scanner.py operationalizes this by scanning IPs/CIDRs and common ports, checking liveness, fingerprinting likely cameras, invoking the CVE-2020-25078 checks, and storing recovered credentials in cameras.db. Post-exploitation capability is substantial. telnet_client.py provides raw Telnet login and command execution. botnet.py fans out commands across stored hosts. persistence.py installs SSH authorized_keys, cron, rc.local, init.d, systemd, inittab telnetd, and bind-shell style persistence. reverse_shell.py generates many Linux/IoT reverse shell one-liners and runs listeners. pivot_chain.py and socks_pivot.py support chained execution and local SOCKS5 pivoting through compromised hosts. Additional modules broaden scope beyond the HiSilicon exploit: brute.py and cred_spray.py perform credential attacks across Telnet, SSH, FTP, HTTP, SMB, databases, VNC, LDAP, WinRM, and more; network_exploit.py checks for exposed/misconfigured services and some well-known vulnerabilities such as MS17-010 and BlueKeep; web_exploit.py, web_cves.py, web_bugs.py, and web_brute.py scan websites for exposed files, CMS fingerprints, generic bug classes, and multiple CVE signatures. Recon/intel support includes ASN, DNS, GeoIP, JARM, WAF detection, proxy/Tor rotation, screenshot grabbing from camera snapshot endpoints, and Telegram/Discord/AbuseIPDB integrations. The repository structure is coherent and functional, with many CLI-capable modules and a central web UI in templates/index.html. Overall, this is an operational exploit-and-post-exploitation toolkit focused on HiSilicon IoT devices but expanded into a broader C2-style offensive platform.flags-alt · Disclosed May 20, 2026 · python · html · network · web · localOperationalCVE-2024-21893.pyThis repository contains a Python proof-of-concept exploit for CVE-2024-21893, a server-side request forgery (SSRF) vulnerability in the SAML component of Ivanti Connect Secure, Policy Secure, and Neurons for ZTA. The exploit script (CVE-2024-21893.py) constructs a malicious SAML SOAP request with a crafted <ds:RetrievalMethod> URI pointing to an attacker-controlled server. When sent to the vulnerable endpoint (typically /dana-ws/saml20.ws), the target system processes the XML and makes a server-side request to the specified URI, enabling the attacker to access internal resources or exfiltrate data. The script supports both single-target and list-based targeting and requires the attacker to specify their own server for receiving SSRF callbacks. The README provides usage instructions, example payloads, and references. The exploit is a functional PoC and does not include weaponized features such as automated post-exploitation or payload customization.h4x0r-dz · Disclosed Feb 2, 2024 · python · markdown · networkPoC
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
IvantiConnect Secureapplication
IvantiNeurons For Zero-Trust Accessapplication
IvantiPolicy Secureapplication
FAQ

Frequently asked questions

Is CVE-2024-21893 exploited in the wild?
Yes. As of Nov 2, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Jan 31, 2024.
Is there a public exploit for CVE-2024-21893?
Yes. Mallory tracks 4 public exploits or proofs of concept for CVE-2024-21893, the earliest disclosed Jan 31, 2024.
Is there a patch for CVE-2024-21893?
Upgrade affected deployments to the latest vendor-supported patched release for the applicable product and release branch. Ivanti's February 8 and February 14, 2024 updates superseded the January 31 and February 1 patches; do not rely on those initial builds as the final remediation baseline.
What products are affected by CVE-2024-21893?
Ivanti Connect Secure, Ivanti Policy Secure, and Ivanti Neurons For Zero-Trust Access.
How severe is CVE-2024-21893?
CVE-2024-21893 has a CVSS v3.1 score of 8.2 (High) and an EPSS score of 100.0% (100th percentile) as of Nov 2, 2026.
Activity feed

Recent activity

61 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+38 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence20Every report linking this CVE to a named adversary.
Associated malware34Malware families linked to this CVE, with evidence and IOCs.
Detection signatures4YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity5Community discussion across Reddit, Mastodon, and other social sources.