dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 2 Feb 2024. Known ransomware use
Connect SecureApplication · Ivanti

CVE-2024-21893

HIGH · 8.2 CVSS v3.1 Published 2024-01-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a server-side request forgery (SSRF) vulnerability in the SAML component of Ivanti Connect Secure, Policy Secure, and Ivanti Neurons for ZTA. The flaw allows unauthenticated remote attackers to trick the affected devices into making arbitrary HTTP requests to internal or external resources, bypassing authentication controls.

MitigationApply vendor-provided patches for affected versions (9.x, 22.x) as soon as they are released. Additionally, restrict administrative access to trusted networks, implement network segmentation to limit SSRF impact, and monitor SAML endpoint traffic for anomalies.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Connect SecureApplication
Affected:= 9.0= 9.1= 21.9= 21.12= 22.1= 22.2= 22.3= 22.4= 22.6
Policy SecureApplication
Affected:= 9.0= 9.1= 22.1= 22.2= 22.3= 22.4= 22.5= 22.6
Neurons For Zero Trust AccessApplication
Affected:all versions= 22.2= 22.3= 22.4= 22.5= 22.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Ivanti product in use
    Determine which Ivanti product is deployed: Ivanti Connect Secure, Ivanti Policy Secure, or Ivanti Neurons for Zero Trust Access. Check the product name in the admin console or system information.
    Affected if The product is one of these three: Connect Secure, Policy Secure, or Neurons for ZTA.
  2. Check the installed version
    Locate the version number in the product admin interface under System > Configuration > System Management, or use the command line and check the release notes or the /etc/version file if accessible. Compare your version against the affected list: Connect Secure versions 9.0, 9.1, 21.9, 21.12, 22.1, 22.2, 22.3, 22.4, 22.6; Policy Secure versions 9.0, 9.1, 22.1, 22.2, 22.3, 22.4, 22.5, 22.6; Neurons for ZTA all versions and specifically 22.2, 22.3, 22.4, 22.5, 22.6.
    Affected if Your installed version matches one of the versions listed in the affected products.
  3. Verify SAML configuration is active
    In the admin console, navigate to Authentication > Auth Servers or Users > User Authentication > SAML and confirm whether SAML authentication is configured or enabled. For Ivanti Connect Secure, check under Authentication > SAML; for Policy Secure, check under Users > User Authentication > SAML.
    Affected if SAML authentication is enabled or configured on the device.
  4. Review SAML endpoint logs for anomalies
    Access the system logs or SAML-specific logs through the admin console under Maintenance > Troubleshooting > Logs, or via the command line if available. Look for unexpected or unusual requests to the SAML endpoint that may indicate exploitation attempts.
    Affected if Unexpected SAML requests are observed in logs, especially from unauthenticated sources targeting the SAML interface.

You are affected if you are running any of the listed Ivanti product versions with SAML enabled, as the SSRF vulnerability exists in the SAML component and can be exploited without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-provided patches for affected versions (9.x, 22.x) as soon as they are released. Additionally, restrict administrative access to trusted networks, implement network segmentation to limit SSRF impact, and monitor SAML endpoint traffic for anomalies.

Recommended fix High confidence

Upgrade to the latest available Ivanti release (Connect Secure 22.3+, Policy Secure 22.3+, or Neurons for ZTA 22.5+) - consult Ivanti KB for exact fixed versions per product branch

  1. 1. Identify the exact Ivanti product and version currently deployed from the affected list (Connect Secure, Policy Secure, or Neurons for ZTA).
  2. 2. Consult Ivanti's official security advisory at forums.ivanti.com or vendor documentation for the specific fixed release corresponding to your product version.
  3. 3. Plan maintenance window for upgrade - schedule during low-traffic period.
  4. 4. Backup current configuration before performing upgrade.
  5. 5. Download the patched version from Ivanti's support portal.
  6. 6. Apply the upgrade following Ivanti's standard upgrade procedure for your product.
  7. 7. After upgrade, verify the SAML component functions correctly and the vulnerability is remediated.
  8. 8. Confirm the new version is no longer in the affected versions list.
Caveat Review Ivanti release notes for your product version for any configuration or behavioral changes that may require adjustment after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Connect Secure Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-21893 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-21893 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data