dbcve.org
Connect SecureApplication · Ivanti

CVE-2024-22024

HIGH · 8.3 CVSS v3.1 Published 2024-02-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
92/100
Remediation priority · Urgent
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
An XML external entity or XXE vulnerability in the SAML component of Ivanti Connect Secure (9.x, 22.x), Ivanti Policy Secure (9.x, 22.x) and ZTA gateways which 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 an XML External Entity (XXE) injection vulnerability in the SAML authentication component of Ivanti Connect Secure, Ivanti Policy Secure, and ZTA gateways. The flaw allows unauthenticated attackers to craft malicious SAML XML requests containing external entity references to access restricted resources without proper authentication, potentially bypassing the entire authentication mechanism.

MitigationApply vendor-provided patches or upgrade to fixed versions of the affected products. Until patches are applied, consider restricting access to SAML endpoints at the network level or implementing XML input validation/filtering as a temporary workaround.

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.1= 22.4= 22.5
Policy SecureApplication
Affected:= 22.5
Zero Trust Access GatewayApplication
Affected:= 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
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 installed Ivanti product
    Access the device admin interface or check system documentation to determine which product is deployed: Ivanti Connect Secure, Ivanti Policy Secure, or Ivanti Zero Trust Access Gateway.
    Affected if The product is one of these three and the version matches the affected ranges.
  2. Determine the installed software version
    Log into the admin console and navigate to System > Status or use the CLI command 'show version' to retrieve the exact firmware version number.
    Affected if The version is 9.1, 22.4, or 22.5 for Connect Secure; 22.5 for Policy Secure; or 22.6 for Zero Trust Access Gateway.
  3. Verify SAML authentication is configured
    Check the authentication policy settings in the admin interface under Users > Authentication > Auth Servers or System > Authentication > SAML, and confirm whether any SAML identity provider (IdP) is defined and enabled.
    Affected if SAML authentication is actively configured and users can authenticate via SAML.
  4. Inspect SAML configuration files
    Access the device configuration backup or view XML configuration files under /var/log/ or the admin-exported configuration for SAML-related XML content containing entity definitions.
    Affected if The device accepts SAML XML requests and external entity processing is not explicitly disabled in the XML parser settings.

A user is affected if they are running one of the listed product versions AND have SAML authentication enabled, as the vulnerability requires both conditions to be exploitable.

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 or upgrade to fixed versions of the affected products. Until patches are applied, consider restricting access to SAML endpoints at the network level or implementing XML input validation/filtering as a temporary workaround.

Recommended fix Moderate confidence

Latest patched release (contact Ivanti support for specific version number)

  1. 1. Identify the exact installed version of Ivanti Connect Secure, Policy Secure, or Zero Trust Access Gateway using the admin console or system information
  2. 2. Confirm the version matches one of the affected releases: Connect Secure (9.1, 22.4, 22.5), Policy Secure (22.5), or ZTA Gateway (22.6)
  3. 3. Download and apply the latest Ivanti security patch for your specific product from the official Ivanti download portal or support site
  4. 4. After patching, verify the SAML configuration is intact and test authentication flows
  5. 5. Monitor Ivanti forums and security advisories for any additional required updates
Caveat Review release notes for any configuration changes required after applying the security patch

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

Fix this in Connect Secure Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-22024 — 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-22024 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