dbcve.org
IdentityiqApplication · Sailpoint

CVE-2024-2228

HIGH · 8.8 CVSS v3.1 Published 2024-03-22
Fix available
A fix is available. Upgrade to 8.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
This vulnerability allows an authenticated user to perform a Lifecycle Manager flow or other QuickLink for a target user outside of the defined QuickLink Population.

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

This is an authentication bypass/authorization vulnerability in QuickLink functionality where an authenticated user can perform Lifecycle Manager flows or other QuickLink actions for target users outside their permitted QuickLink Population. The system fails to properly validate that the target user belongs to the caller's defined population before allowing the operation.

MitigationImplement and enforce population membership validation in the QuickLink and Lifecycle Manager authorization checks to ensure users can only access resources within their defined QuickLink Population.

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
IdentityiqApplication
Affected:< 8.1= 8.1= 8.2= 8.3= 8.4

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 IdentityIQ version
    Check the IdentityIQ installation directory for the version file, typically in the config folder or via the system information page in the UI. Common locations includeIdentityIQ_HOME/config/identityiq.properties or the about page in the administrative console.
    Affected if The installed version is 8.1, 8.2, 8.3, 8.4, or any version below 8.1.
  2. Verify QuickLink module is enabled
    Navigate to IdentityIQ Administration > QuickLinks or check the application configuration for QuickLink module status. Review the iiq.conf or identityiq.properties configuration files for QuickLink-related settings.
    Affected if QuickLink functionality is enabled and accessible to users.
  3. Confirm Lifecycle Manager access via QuickLink
    Review the QuickLink definitions in the IdentityIQ console to determine if Lifecycle Manager operations are exposed as QuickLink actions accessible to end users.
    Affected if Lifecycle Manager can be invoked through QuickLink functionality.
  4. Review QuickLink Population definitions
    Access IdentityIQ Administration > QuickLink Populations to examine the population definitions. Check which populations exist and which users are assigned to each population.
    Affected if QuickLink Populations are defined and users are assigned to them.
  5. Check authorization configuration for QuickLink operations
    Review the QuickLink and Lifecycle Manager authorization configuration in IdentityIQ to determine if population membership validation is enforced. Examine the access certification or entitlement configuration related to QuickLink actions.
    Affected if Authorization checks do not properly validate that the target user belongs to the caller's defined QuickLink Population before allowing the operation.

You are affected if IdentityIQ version 8.1 through 8.4 (or below 8.1) is installed, QuickLink functionality is enabled, and the system allows users to perform operations on target users outside their QuickLink Population without proper validation.

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 8.1 or later
Fixed in 8.1
Interim mitigation

Implement and enforce population membership validation in the QuickLink and Lifecycle Manager authorization checks to ensure users can only access resources within their defined QuickLink Population.

Recommended fix Moderate confidence

IdentityIQ 8.4 or later (contact SailPoint for exact fixed release)

  1. Contact SailPoint support or visit www.sailpoint.com to obtain the latest security patch for IdentityIQ
  2. Apply the patch following SailPoint's standard patch deployment procedures
  3. Verify the patch was applied successfully by checking the IdentityIQ version
  4. Test the Lifecycle Manager and QuickLink functionality to confirm the vulnerability is remediated

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

Fix this in Identityiq 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-2024-2228 — 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-2228 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