Security Resilience

CVE-2024-10905

Sailpoint Identityiq ≤ 8.2

Published
02 December 2024
Modified
12 November 2025
Patch / advisory
View advisory
CVSS Score v3.1 10.0
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS Score 0.0094 60th percentile
Risk Priority 76 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-10905 is a critical-severity Improper Handling of File Names that Identify Virtual Resources (CWE-66) vulnerability in Sailpoint Identityiq. Its CVSS base score is 10.0 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked in the top 40% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

IdentityIQ 8.4 and all 8.4 patch levels prior to 8.4p2, IdentityIQ 8.3 and all 8.3 patch levels prior to 8.3p5, IdentityIQ 8.2 and all 8.2 patch levels prior to 8.2p8, and all prior versions allow HTTP/HTTPS access to static content…

more

in the IdentityIQ application directory that should be protected.

CWE(s)
CWE-66

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001 Data Obfuscation Command And Control
Adversaries may obfuscate command and control traffic to make it more difficult to detect.
attack.mitre.org →
T1001.002 Steganography Command And Control
Adversaries may use steganographic techniques to hide command and control traffic to make detection efforts more difficult.
attack.mitre.org →
T1001.003 Protocol or Service Impersonation Command And Control
Adversaries may impersonate legitimate protocols or web service traffic to disguise command and control activity and thwart analysis efforts.
attack.mitre.org →
T1003.004 LSA Secrets Credential Access
Adversaries with SYSTEM access to a host may attempt to access Local Security Authority (LSA) secrets, which can contain a variety of different credential materials, such as credentials for service accounts.
attack.mitre.org →
T1003.006 DCSync Credential Access
Adversaries may attempt to access credentials and other sensitive information by abusing a Windows Domain Controller's application programming interface (API)(Citation: Microsoft DRSR Dec 2017) (Citation: Microsoft GetNCCChanges) (Citati…
attack.mitre.org →
T1006 Direct Volume Access Stealth
Adversaries may directly access a volume to bypass file access controls and file system monitoring.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-32217Same product: Sailpoint Identityiq
CVE-2025-10280Same product: Sailpoint Identityiq
CVE-2024-2227Same product: Sailpoint Identityiq
CVE-2024-1714Same product: Sailpoint Identityiq
CVE-2026-5712Same product: Sailpoint Identityiq
CVE-2026-12341Same product: Sailpoint Identityiq
CVE-2024-2228Same product: Sailpoint Identityiq

Affected Assets

sailpoint
identityiq
8.2, 8.3, 8.4 · ≤ 8.2

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

Validating file name inputs structurally stops acceptance of names that resolve to unintended virtual resources.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles such as input validation and complete mediation prevent mishandling of virtual file names during design.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 partial match
blocks

Secure SDLC practices directly require input validation and safe file-handling routines that prevent virtual-resource path issues.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.19 Installation of software on operational systems partial match
removes
A.8.25 Secure development life cycle partial match
blocks

Secure development lifecycle practices can include input validation and path-handling rules that reduce the risk of mishandling virtual file names.

A.8.26 Application security requirements partial match
blocks

A.8.26 only requires that security requirements (including resilience against injections or input controls) be identified and specified during development or acquisition; it does not itself enforce, implement, or stop exploitation of improper virtual file name handling.

A.8.27 Secure system architecture and engineering principles partial match
blocks

Secure system architecture and engineering principles can incorporate design controls that prevent improper resolution of virtual file names.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly address safe file-name handling and canonicalization, substantially mitigating this weakness.

A.8.29 Security testing in development and acceptance partial match
finds

Security testing in development can detect path-traversal or virtual-resource handling flaws before deployment.

References