CVE-2024-1524
Auth Bypass in Wso2 Identity Server 6.0.0 – 6.0.0.171
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:LCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-1524 is a high-severity Authentication Bypass by Spoofing (CWE-290) vulnerability in Wso2 Identity Server. Its CVSS base score is 7.7 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); ranked at the 18th 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 IA-3 (Device Identification and Authentication) — 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-1524 affects deployments using the "Silent Just-In-Time Provisioning" feature enabled for a federated identity provider (IDP), as detailed in WSO2 security advisories. The vulnerability arises during the account provisioning process, where a local user store's user information may be replaced if federated users share the same username as existing local users. There is no impact unless an IDP is configured for federated authentication with Silent JIT provisioning specifically enabled.
A malicious actor can exploit this vulnerability if they possess a fresh valid user account in the federated IDP that has not been used earlier, knowledge of a valid local IDP username, and control of a federated IDP account matching that targeted local username. Successful exploitation allows the actor to associate the targeted local user account with their controlled federated IDP account, replacing local user information. The CVSS score of 7.7 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L) reflects high confidentiality and integrity impacts with low availability impact, mapped to CWE-290.
The WSO2 security advisory provides details on mitigations at https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3144/.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-17272
Vulnerability Data
When the "Silent Just-In-Time Provisioning" feature is enabled for a federated identity provider (IDP) there is a risk that a local user store user's information may be replaced during the account provisioning process in cases where federated users share the…
more
same username as local users. There will be no impact on your deployment if any of the preconditions mentioned below are not met. Only when all the preconditions mentioned below are fulfilled could a malicious actor associate a targeted local user account with a federated IDP user account that they control. The Deployment should have: -An IDP configured for federated authentication with Silent JIT provisioning enabled. The malicious actor should have: -A fresh valid user account in the federated IDP that has not been used earlier. -Knowledge of the username of a valid user in the local IDP. -An account at the federated IDP matching the targeted local username.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 3 hardening rules · 3 OS baselines
V6.4.3V10.4.16V11.4.3
Mitigating Controls (NIST 800-53 r5) AI
Proper unique identification and authentication of users directly stops spoofing-based bypass of authentication.
Device identification and authentication before connection prevents spoofing of devices to bypass auth.
Authentication of non-organizational users blocks external spoofing attempts against the scheme.
Authenticator management ensures credentials cannot be easily spoofed or reused to bypass authentication.
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.
Proofing and binding identities reduces spoofing opportunities during enrollment but does not address runtime authentication implementation flaws.
Requiring authentication of users/services/hardware directly counters spoofing-based bypass when strong methods are used.
Protecting, conveying, and verifying identity assertions specifically prevents the spoofing that enables authentication bypass.
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.5.15 only requires that an access control policy and requirements be defined and communicated; it does not itself implement, enforce or configure any authentication scheme that would stop spoofing attacks from bypassing authentication, so the weakness remains fully exploitable.
A.5.16 manages the lifecycle, uniqueness, and accountability of identities; it does not implement or strengthen authentication schemes against spoofing, so the CWE-290 exploit remains possible even when identities are correctly provisioned and tracked.
Authentication information management directly addresses credential handling that prevents spoofing.
A.5.18 governs the provisioning, review, and revocation of already-granted access rights to authenticated identities; it has no bearing on whether an authentication scheme can be spoofed or bypassed before any rights are assigned.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (higher-evidence rows only; rows rated `none` are excluded).
Oracle Linux 8 (1 rule)
- V-248827 OL 8 must not have the rsh-server package installed. blocks CWE-290
RHEL 7 (1 rule)
- V-204442 The Red Hat Enterprise Linux operating system must not have the rsh-server package installed. blocks CWE-290
RHEL 8 (1 rule)
- V-230492 RHEL 8 must not have the rsh-server package installed. blocks CWE-290