CVE-2024-56404
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2024-56404 is a critical-severity Authentication Bypass by Assumed-Immutable Data (CWE-302) vulnerability in Oneidentity (inferred from references). Its CVSS base score is 9.9 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 48th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to IA-2 (Identification and Authentication (Organizational Users)) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-56404 is an insecure direct object reference (IDOR) vulnerability, mapped to CWE-302, in One Identity Identity Manager 9.x versions before 9.3. Only on-premise installations are affected. The issue enables privilege escalation and carries a CVSS v3.1 base score of 9.9 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H), marking it as critical due to its network accessibility, low complexity, low privilege requirements, lack of user interaction, and high impacts across confidentiality, integrity, availability, and scope.
An authenticated attacker with low privileges can exploit this IDOR flaw remotely to escalate privileges. Exploitation requires no user interaction and can lead to full compromise of the targeted system, granting high-level access and potentially disrupting or extracting sensitive identity management data.
Vendor advisories recommend upgrading to One Identity Identity Manager 9.3, where the vulnerability is addressed, as outlined in the product notification at https://support.oneidentity.com/product-notification/noti-00001678 and the 9.3 release notes at https://support.oneidentity.com/technical-documents/identity-manager/9.3/release-notes/. Further details are available on the One Identity community forum at https://www.oneidentity.com/community/identity-manager/.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-53137
Vulnerability Data
In One Identity Identity Manager 9.x before 9.3, an insecure direct object reference (IDOR) vulnerability allows privilege escalation. Only On-Premise installations are affected.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V7.2.4
Mitigating Controls (NIST 800-53 r5) AI
Mandates proper unique identification and authentication of users, precluding reliance on attacker-controlled immutable assumptions.
Requires server-side enforcement of authorizations instead of trusting client-supplied mutable data for authentication decisions.
Mandates proper identification and authentication for non-organizational users, precluding reliance on attacker-controlled immutable assumptions.
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.
Strong authentication mechanisms directly avoid reliance on attacker-controlled immutable data.
Protecting and verifying identity assertions prevents tampering with data assumed immutable during auth.
Least-privilege authorization policies reduce impact of bypassed authentication but do not address the root flaw.
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.
Security testing can discover and block authentication bypasses that rely on mutable data.
Access-control policy can mandate validation of all identity data, reducing reliance on assumed-immutable fields.
Identity-management processes can require verification of mutable attributes, mitigating the root cause.
Proper management of authentication information prevents use of client-controlled tokens or cookies as sole proof of identity.
Access-rights reviews can detect and revoke rights granted via tampered immutable data.
Secure SDLC practices include threat modeling and input-validation requirements that catch assumed-immutable data flaws.