CVE-2024-1524: A local user can be impersonated when using federated authentication with Silent JIT Provisioning.
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 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.
Affected Software
Remediation
Information
Event History
Frequently Asked Questions
What is the severity of CVE-2024-1524?
CVE-2024-1524 has been classified as a high severity vulnerability due to the potential for local user impersonation.
How do I fix CVE-2024-1524?
To fix CVE-2024-1524, disable the Silent Just-In-Time Provisioning feature in your federated identity provider settings.
Who is affected by CVE-2024-1524?
CVE-2024-1524 affects users of WSO2 API Manager versions up to 4.2.0 and WSO2 Identity Server versions up to 6.1.0.
What are the consequences of exploiting CVE-2024-1524?
Exploiting CVE-2024-1524 could allow an attacker to impersonate local users, leading to unauthorized access to sensitive information.
When was CVE-2024-1524 disclosed?
CVE-2024-1524 was disclosed in 2024, highlighting a critical security issue for users of WSO2 products.