CVE-2024-1714: Access Request for Entitlement Values with Leading/Trailing Whitespace
Published Feb 21, 2024
·Updated
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
Affected Software
15 affected components
IdentityIQ Lifecycle Manager<=
SailPoint IdentityIQ=8.1
SailPoint IdentityIQ=8.1-patch1
SailPoint IdentityIQ=8.1-patch2
SailPoint IdentityIQ=8.1-patch3
SailPoint IdentityIQ=8.1-patch4
SailPoint IdentityIQ=8.1-patch5
SailPoint IdentityIQ=8.1-patch6
SailPoint IdentityIQ=8.2
SailPoint IdentityIQ=8.2-patch1
SailPoint IdentityIQ=8.2-patch2
SailPoint IdentityIQ=8.2-patch4
SailPoint IdentityIQ=8.3
SailPoint IdentityIQ=8.3-patch1
SailPoint IdentityIQ=8.4
Event History
Feb 21, 2024
CVE Published
via MITRE·04:57 PM
Data Sourced
via MITRE·04:57 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:15 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the significance of CVE-2024-1714 being rejected or withdrawn?
CVE-2024-1714 being rejected means it's no longer recognized as a valid vulnerability and does not pose a security risk.
2
How does the rejection of CVE-2024-1714 affect users of IdentityIQ Lifecycle Manager?
Users of IdentityIQ Lifecycle Manager are not required to take action based on CVE-2024-1714 since it has been withdrawn.
3
What should I do if I believe I am affected by an issue related to CVE-2024-1714?
If you believe there is a related issue, contact SailPoint Support for further guidance and assistance.
4
Where can I find information regarding other vulnerabilities in IdentityIQ Lifecycle Manager?
Information on other vulnerabilities can typically be found in security advisories directly from SailPoint or similar sources.
5
Is there a patch or remediation for CVE-2024-1714?
Since CVE-2024-1714 has been rejected, there is no patch or remediation required.