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

> An attacker can exploit a server-side request forgery in Ivanti Connect Secure to access restricted resources without authentication.

- **Severity:** High 8.2 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Yes, since 31 Jan 2024 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jan 2024
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-5rr9-mqhj-7cr2

## What is CVE-2024-21893?

CVE-2024-21893 is a high-severity server-side request forgery vulnerability in Ivanti Connect Secure, published on 31 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2024-21893?

It affects 3 products.


Products: Ivanti Connect Secure, Ivanti Neurons for Zero-Trust Access, Ivanti Policy Secure.

## How do I fix CVE-2024-21893?

No fix has been published for CVE-2024-21893 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 2 Feb 2024.

## Is CVE-2024-21893 being exploited?

Yes. Attackers have exploited CVE-2024-21893 in the wild since at least 31 Jan 2024, including in ransomware campaigns.

Public exploit code:

- CVE-2024-21893: SSRF Vulnerability in Ivanti Connect Secure (github_poc): https://github.com/h4x0r-dz/CVE-2024-21893.py
- CVE-2024-21893 to CVE-2024-21887 Exploit Toolkit (github_poc): https://github.com/Chocapikk/CVE-2024-21893-to-CVE-2024-21887
- Ivanti Connect Secure Unauthenticated Remote Code Execution (metasploit)
- Ivanti SAML - Server Side Request Forgery (SSRF) (nuclei): http/cves/2024/CVE-2024-21893.yaml

## Other vulnerabilities in Ivanti Connect Secure

- [CVE-2021-22893](https://insights.sbomify.com/CVE-2021-22893/): Ivanti Pulse Connect Secure Use-After-Free (critical 10.0, exploited in the wild)
- [CVE-2019-11510](https://insights.sbomify.com/CVE-2019-11510/): Ivanti Pulse Connect Secure Arbitrary File Read (critical 9.9, exploited in the wild)
- [CVE-2024-21887](https://insights.sbomify.com/CVE-2024-21887/): Ivanti Connect Secure and Policy Secure Command Injection (critical 9.1, exploited in the wild)
- [CVE-2025-22457](https://insights.sbomify.com/CVE-2025-22457/): Ivanti Connect Secure, Policy Secure, and ZTA Gateways Stack-Based Buffer Overflow (critical 9.0, exploited in the wild)
- [CVE-2025-0282](https://insights.sbomify.com/CVE-2025-0282/): Ivanti Connect Secure, Policy Secure, and ZTA Gateways Stack-Based Buffer Overflow (critical 9.0, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-21893 and fix it if it is affected.

What it is: CVE-2024-21893 is a high-severity server-side request forgery vulnerability in Ivanti Connect Secure, published on 31 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2024-21893 in the wild since at least 31 Jan 2024, including in ransomware campaigns.

Affected product: Ivanti Connect Secure. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-21893/ (Markdown: https://insights.sbomify.com/CVE-2024-21893/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-21893
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-21893
- OSV: https://osv.dev/vulnerability/CVE-2024-21893

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-21893/
Summaries are generated and may contain mistakes; the official description above is the record.