dbcve.org
Okta SsoApplication · Sysaid

CVE-2022-23170

CRITICAL · 9.8 CVSS v3.1 Published 2022-06-24
Fix available
A fix is available. Upgrade to after 22.1.63 or later.
See remediation →
100/100
Remediation priority · Urgent
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
SysAid - Okta SSO integration - was found vulnerable to XML External Entity Injection vulnerability. Any SysAid environment that uses the Okta SSO integration might be vulnerable. An unauthenticated attacker could exploit the XXE vulnerability by sending a malformed POST request to the identity provider endpoint. An attacker can extract the identity provider endpoint by decoding the SAMLRequest parameter's value and searching for the AssertionConsumerServiceURL parameter's value. It often allows an attacker to view files on the application server filesystem and interact with any back-end or external systems that the application can access. In some situations, an attacker can escalate an XXE attack to compromise the underlying server or other back-end infrastructure by leveraging the XXE vulnerability to perform server-side request forgery (SSRF) attacks.

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

XXE vulnerability in SysAid's Okta SSO integration allows unauthenticated attackers to send malformed POST requests to the identity provider endpoint. By decoding the SAMLRequest parameter to locate the AssertionConsumerServiceURL, attackers can extract files from the server filesystem and interact with back-end systems, potentially escalating to SSRF.

MitigationDisable or restrict access to the Okta SSO integration until an official patch is available; if possible, disable external entity processing in the SAML XML parser configuration.

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
Okta SsoApplication
Affected:>= 22.1.49, <= 22.1.63

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
High
Availability
High

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

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 SysAid installation version
    Locate the SysAid installation directory and check the version file or About page within the application. Common locations include the installation folder or the server's web application metadata.
    Affected if The installed version is >= 22.1.49 and <= 22.1.63
  2. Confirm Okta SSO integration is configured
    Navigate to SysAid admin settings and check if Okta SSO integration has been enabled. Look for identity provider settings or SSO configuration related to Okta.
    Affected if Okta SSO integration is enabled or partially configured in SysAid
  3. Verify SAMLRequest endpoint accessibility
    Check if the identity provider endpoint (typically found under SSO/Okta settings) accepts POST requests. Examine whether the SAMLRequest parameter can be manipulated in incoming authentication requests.
    Affected if The SAML endpoint accepts unauthenticated POST requests with SAMLRequest parameters
  4. Check for XXE vulnerability indicators
    Review application logs for unusual XML parsing errors or failed authentication attempts that may indicate XXE exploitation attempts. Monitor for unexpected outbound connections or file access patterns.
    Affected if Logs show XML parsing errors, unusual file access attempts, or SSRF-like outbound connections from the server

You are affected if SysAid version is between 22.1.49 and 22.1.63 inclusive AND the Okta SSO integration is enabled or accessible.

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
Upgrade available Upgrade to a release after 22.1.63
Interim mitigation

Disable or restrict access to the Okta SSO integration until an official patch is available; if possible, disable external entity processing in the SAML XML parser configuration.

Recommended fix Moderate confidence

SysAid version > 22.1.63 (latest stable release)

  1. 1. Identify current SysAid Okta SSO integration version by checking the SysAid server administration console or system information.
  2. 2. Confirm the installed version falls within the vulnerable range: 22.1.49 through 22.1.63.
  3. 3. Obtain the latest stable SysAid release from the official vendor (SysAid / Ivanti) which should contain the security fix for this XXE vulnerability.
  4. 4. Before applying the upgrade, perform a full backup of the SysAid database and configuration files.
  5. 5. Test the upgrade in a staging environment to verify Okta SSO functionality works correctly.
  6. 6. Apply the upgrade to production during a scheduled maintenance window.
  7. 7. Verify the Okta SSO integration is functioning by attempting a test login through Okta.
Caveat Minor: Review release notes for any changes to Okta SSO configuration requirements; ensure SAML settings remain compatible

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

Fix this in Okta Sso Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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