CVE-2024-21893

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.

CVSS: 8.2Highscored by the publisher (CNA)
Exploited in the wild: Yes, in CISA KEV since 31 Jan 2024CISA deadline for US federal agencies: 2 Feb 2024known use in ransomware campaignspublic exploit code
EPSS: > 99.9%chance of exploitation in the next 30 daystop 0.1% of scored CVEsFIRST score of 11 Nov 2026
Fix: Patch availablesee the advisories in the references
Published: 31 Jan 2024analysed here 12 Nov 2026

Do first. Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. (CISA's required action for this KEV entry)

Summary

Triage

Attack surface: Server-side
Exploitable: At runtime
Attack vector: network
Weakness: CWE-918 Server-Side Request Forgery (SSRF)

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

Product	Affected versions	Vendor says fixed in
Ivanti ICS	<= 9.1R18<= 22.6R2Vendor says fixed in: not stated	Not stated by the vendor
Ivanti IPS	<= 9.1R18<= 22.6R1Vendor says fixed in: not stated	Not stated by the vendor

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

ivanti:connect_secure
ivanti:policy_secure
ivanti:neurons_for_zero-trust_access

Fix and mitigation

WAF and other mitigations

Can a WAF block it? Partly. SSRF makes the server call a URL the attacker picks. A WAF can block well-known targets such as cloud metadata addresses, but not every internal host.

Also consider: egress filter · IMDSv2

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog: Listed since 31 Jan 2024. Known use in ransomware campaigns.
CISA due date: 2 Feb 2024, the remediation deadline for US federal agencies
CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Public exploit code: Yes: 1 Metasploit module · 2 GitHub proofs of concept · 1 Nuclei template
CISA SSVC: exploitation active, automatable yes, technical impact partialAssessed by CISA 31 Jan 2024 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

31 Jan 2024Added to CISA KEV (exploited in the wild)
31 Jan 2024CISA SSVC assessment: exploitation activesame day later
31 Jan 2024Published1 day later
2 Feb 2024First public exploit or proof of concept1 day later
2 Feb 2024CISA remediation due date (US federal agencies)same day later
4 Aug 2026CVE record last updated914 days (about 3 years) later
12 Nov 2026Analysed by vulneraibility.com100 days (about 3 months) later

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Metric	Value	What it means
Attack vector	NetworkReachable over the internet or any routable network.	Reachable over the internet or any routable network.
Attack complexity	LowRepeatable attack, no special conditions.	Repeatable attack, no special conditions.
Privileges required	NoneThe attacker needs no prior access.	The attacker needs no prior access.
User interaction	NoneNo victim action needed.	No victim action needed.
Scope	UnchangedImpact stays within the vulnerable component.	Impact stays within the vulnerable component.
Confidentiality	HighTotal data disclosure possible.	Total data disclosure possible.
Integrity	LowLimited modification possible.	Limited modification possible.
Availability	NoneThe service stays up.	The service stays up.

Common questions

Is CVE-2024-21893 being exploited?

Yes. CVE-2024-21893 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2024-21893?

CVE-2024-21893 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2024-21893?

Yes. A fix has been recorded for CVE-2024-21893. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2024-21893 affect?

CVE-2024-21893 affects ivanti:connect_secure, ivanti:policy_secure, ivanti:neurons_for_zero-trust_access. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVD CVE.org CVE Details Source

2 references in the CVE record, grouped by the tags the record gives them.

Where the data on this page comes from

CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
NVD: CVSS and CPE data
CISA KEV catalog: exploitation, date added, due date
CISA Vulnrichment (ADP): SSVC decision points
FIRST EPSS: exploit probability and percentile
Metasploit Framework: exploit and scanner modules
Nuclei templates: detection templates
PoC-in-GitHub: GitHub repositories that claim a proof of concept

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.