Start with Identity
Identity CVE · SCIM / Provisioning

CVE-2024-3318SailPoint ISC connector path traversal

high
Product: SailPoint Identity Security CloudVendor: SailPointDisclosed: 2024-04-10Status: PatchedProtocol deep diveNVD ↗

What broke

An ISC connector accepted a path it should have rejected and read or wrote outside the intended file set. SailPoint patched. This is the closest thing the 2025-2026 window had to a SCIM / provisioning CVE: not the protocol, the connector.

Why it matters

Provisioning connectors hold service credentials to AD, Entra, HR, and SaaS. A path traversal there is how an IGA admin (or an attacker who became one) reads those credentials off disk.

What to do

  • Confirm the ISC connector fix in your tenant.
  • Rotate connector service accounts. Treat them as tier-zero.
  • Do not let custom connector code read arbitrary paths "for debugging."

After you patch

Provisioning interfaces create and modify accounts, so a flaw here is an account-creation primitive rather than a data leak.

  • Rotate the SCIM bearer token or client credential used by the identity provider.
  • Reconcile provisioned accounts against the authoritative source and remove anything with no matching identity. See orphaned account.
  • Review group membership changes applied through the connector during the window.
  • Confirm deactivation semantics: verify that active: false actually removes access in the target application rather than soft-deleting a still-usable account. See SCIM 2.0.

Sources

Last reviewed By SWI Community TeamSuggest a correctionHow we research
Know a primary source we should add, or a patch status that has changed? Email community@startwithidentity.com. See all briefs in the identity CVE catalog, or volunteer as a CVE Analyst.
Compiled from vendor advisories, NVD, CISA KEV, and public research. CVSS figures can disagree across NVD and the CNA. Confirm affected versions against the vendor advisory before you patch. Independent, community-driven analysis. See the disclaimer.