Veille CVE

Recherche « WSO2 Carbon Identity Oauth »

3 CVE

Critique 0 Élevée 0 Moyenne 2 Faible 0 Non évaluée 1 Exploitées (KEV) Tri : plus récentes « WSO2 Carbon Identity Oauth » ✕
  1. CVE-2025-0326 – Non évaluée

    WSO2 Identity Server · WSO2 Carbon OAuth

    The system fails to invalidate existing access tokens associated with sub-organization users during sensitive account management operations such as password reset, role change, or sub-organization disablement. This oversight allows previously issued tokens to remain active even after the user's access context has been modified or revoked through administrative actions. The identified issue could lead to unauthorized access by a malicious actor, but only when all of the following conditions are met: previously issued access tokens remain active, and these tokens have been exposed to malicious actors.

  2. 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.

  3. 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.