dbcve.org
Connect SecureApplication · Ivanti

CVE-2024-22023

MEDIUM · 5.3 CVSS v3.1 Published 2024-04-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 entity expansion or XEE vulnerability in SAML component of Ivanti Connect Secure (9.x, 22.x) and Ivanti Policy Secure allows an unauthenticated attacker to send specially crafted XML requests in-order-to temporarily cause resource exhaustion thereby resulting in a limited-time DoS.

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 · moderate confidence

An XML entity expansion (XEE) vulnerability exists in the SAML component of Ivanti Connect Secure (9.x, 22.x) and Ivanti Policy Secure. An unauthenticated attacker can send specially crafted XML requests containing nested entity expansions that cause excessive resource consumption, leading to temporary denial of service.

MitigationApply vendor-supplied patches for CVE-2024-22023 when released. As a compensating control, implement XML request size limits and parser entity expansion limits on the SAML IdP/proxy to mitigate resource exhaustion.

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.1= 22.2= 22.3= 22.4= 22.5= 22.6
Policy SecureApplication
Affected:= 9.0= 9.1= 22.1= 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
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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
    Determine whether the system is running Ivanti Connect Secure or Ivanti Policy Secure. This is typically visible in the product UI, admin console, or system documentation.
    Affected if The product is Connect Secure or Policy Secure and the version matches an affected release.
  2. Check the installed software version
    Locate the version number in the product admin interface under System > Configuration > System Management, or check the about/status page. Compare the installed version against the affected list: Connect Secure = 9.1, 22.1, 22.2, 22.3, 22.4, 22.5, 22.6; Policy Secure = 9.0, 9.1, 22.1, 22.2, 22.3, 22.4, 22.5, 22.6.
    Affected if The installed version exactly matches one of the versions in the affected list.
  3. Verify SAML component is in use
    Check if the SAML IdP or SAML proxy feature is enabled on the appliance. This is typically configured under Users > User Realms or Authentication > Auth Servers, or viewed in the SAML configuration section of the admin console.
    Affected if SAML IdP or SAML proxy functionality is configured and active on the device.
  4. Confirm the system accepts XML-based SAML requests
    Determine whether the appliance is configured to process incoming SAML assertions. This can be verified by reviewing the SAML service settings and confirming the system is reachable for SAML authentication traffic.
    Affected if The system processes SAML requests from users or identity providers, making it reachable to the attack vector.

The environment is affected if the installed product is Ivanti Connect Secure or Policy Secure, the version exactly matches one of the listed affected versions, and the SAML component is enabled to process XML-based SAML requests.

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-supplied patches for CVE-2024-22023 when released. As a compensating control, implement XML request size limits and parser entity expansion limits on the SAML IdP/proxy to mitigate resource exhaustion.

Recommended fix Moderate confidence

Connect Secure 22.4+ or Policy Secure 22.3+ (or latest supported 9.x/22.x patch per Ivanti KB)

  1. 1. Log in to the Ivanti Connect Secure or Policy Secure admin console
  2. 2. Navigate to System > Configuration > System Management > License Keys/Updates
  3. 3. Check the current installed version under System Status
  4. 4. Download and install the latest available patch for your major version from Ivanti support portal
  5. 5. Alternatively, upgrade to Connect Secure 22.4 or later, or Policy Secure 22.3 or later which contains the fix
  6. 6. After upgrade, verify the SAML configuration is intact and test authentication flows
  7. 7. Monitor system resources during initial operation to confirm DoS condition is resolved
Caveat Review release notes for any SAML configuration changes between current and target version; test thoroughly in non-production first

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

Fix this in Connect Secure Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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