Access Request for Entitlement Values with Leading/Trailing Whitespace

published 2024-02-21 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-17448

cvss: 7.1; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 28%
public exploits: 0; none known

An issue exists in all supported versions of IdentityIQ Lifecycle Manager that can result if an entitlement with a value containing leading or trailing whitespace is requested by an authenticated user in an access request.

Patch / fix

fixed in 1

SailPoint IdentityIQ 8.2p7, 8.3p4, 8.4p1

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 2 y ago (2024-03-06)

Exploit prediction

0.34% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	7.1	CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:L/A:L
CISA ADP	3.1	7.1	CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:L/A:L

Affected products

SailPoint IdentityIQ

Classification

Weakness

CWE-20 Improper Input Validation

References

sailpoint.com /security-advisories/sailpoint-identityiq-access-request-for-entitlement-values-with-leading-trailing-whitespa
third-party-advisory

Sources

CVE List CVE-2024-1714
NVD CVE-2024-1714

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary