Veille CVE

Recherche « WSO2 Carbon Identity Application »

8 CVE

  1. CVE-2024-6423 4.0 Moyenne

    WSO2 API Manager · WSO2 Open Banking AM · WSO2 Identity Server · WSO2 Identity Server as Key Manager

    The product failed to enforce validation constraints on user-supplied input in URL parameters, allowing sensitive data to be passed to flows where it was not intended to be processed. Although the product did not utilize this data, its acceptance could lead to logging. If a user mistakenly sends sensitive data via URL parameters to any flow, this data could be inadvertently logged in access logs. This has the potential to expose confidential information, compromising the security and privacy of affected systems if the product is used incorrectly.

  2. CVE-2025-13173 6.5 Moyenne

    WSO2 API Control Plane · WSO2 Universal Gateway · WSO2 API Manager · WSO2 Traffic Manager

    Tokens associated with user sessions are not revoked when the corresponding user session is terminated, unless another SSO request is initiated. This occurs when the session-bound token feature is enabled with token binding validation and the "Revoke token upon user logout" option is not active. The software fails to automatically invalidate session-bound tokens upon user session termination. This vulnerability exists when token binding validation is enabled. As a result, a malicious actor possessing a valid session-bound token could exploit this condition to maintain unauthorized access to applications and resources even after the associated user session has ended, potentially leading to the exposure of sensitive user data.

  3. CVE-2024-4412 2.7 Faible

    WSO2 Enterprise Integrator · WSO2 API Manager · WSO2 Open Banking IAM · WSO2 Identity Server

    The software accepts user-supplied data without sufficient validation, allowing for the injection of malicious Expression Language (EL) code. This can lead to the execution of arbitrary operations within the affected deployment. Exploitation of this vulnerability requires administrator privileges. The impact is minimal as EL usage is restricted to certain read operations.

  4. CVE-2025-5802 5.3 Moyenne

    WSO2 API Manager · WSO2 API Control Plane · WSO2 Universal Gateway · WSO2 Traffic Manager

    The self-registration flow accepts user-supplied input for usernames without adequately preventing the disclosure of username existence. When a user attempts to register with an existing username, the system responds with an error message that explicitly indicates the username is already in use. This behavior allows an attacker to discover valid usernames within the system. The discovery of valid usernames can facilitate subsequent attacks such as brute force, social engineering, and targeted phishing campaigns.

  5. CVE-2025-15039 9.4 Critique

    WSO2 Identity Server · WSO2 API Manager · WSO2 Open Banking AM · WSO2 Open Banking IAM

    The Conditional Authentication (Adaptive Authentication) script does not correctly enforce the completion of all required authentication steps when a specific multi-step pattern involving certain authenticators is configured. This allows an attacker to bypass intermediate authentication challenges by exploiting how the script handles callbacks and re-execution of authentication steps. Successful exploitation allows a malicious actor to gain unauthorized access to a targeted user account. This vulnerability can only be exploited when all of the following conditions are met: the application login flow contains a specific secondary authenticator, the Conditional Authentication script is configured with particular event callbacks and re-executes an authentication step, the targeted user has one of the impacted authenticators enrolled, and the attacker successfully completes any preceding authentication steps.

  6. CVE-2025-13909 4.3 Moyenne

    WSO2 Identity Server · WSO2 Carbon Identity Application Authentication Framework · WSO2 Carbon MagicLink Authenticator Module · WSO2 Carbon Abstract OTP Authenticator

    The system accepts authentication requests without sufficient validation to enforce tenant isolation when using Email OTP, SMS OTP, or Magic Link as first-factor authenticators. This failure to adequately separate user data between tenants can lead to the exposure of personally identifiable information. Successful exploitation allows an attacker to disclose personally identifiable information of users in different tenants, resulting in privacy violations and potential regulatory non-compliance. This may include unauthorized access to user details such as mobile numbers.

  7. CVE-2024-10302 5.8 Moyenne

    WSO2 API Control Plane · WSO2 Traffic Manager · WSO2 Universal Gateway · WSO2 API Manager

    The user self-signup flow in multiple WSO2 products fails to adequately validate user-supplied input. This weakness allows arbitrary unvalidated data to be included within user claims, which are then used by downstream processes. Allowing unvalidated input into user claims can lead to various security risks. Malicious or malformed data injected during signup could be processed by other parts of the application, potentially enabling attacks such as content manipulation, redirection, user interface inconsistencies, unauthorized actions, and data exposure. The actual impact depends on how the compromised data is consumed and the privileges associated with the affected users.

  8. CVE-2025-10908 7.3 Élevée

    WSO2 Identity Server · WSO2 Carbon MagicLink Authenticator Module

    Due to a lack of user account state validation during authentication, locked user accounts can be successfully authenticated using Magic Link or Pass Key methods. This bypasses the intended security control that should prevent access to accounts that have been locked. This vulnerability may allow unauthorized access to applications and sensitive data associated with accounts that should have been restricted via the account lock mechanism. It also undermines the effectiveness of the account lock mechanism intended to prevent further login attempts.