CVE-2024-9517
Improper Token Renewal in Refresh Token Grant in Multiple WSO2 Products Allows Unauthorized Access to Blocked Accounts
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N
Fuente: CNA
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | CVE-2024-9517 divulgada · CVSS 4.9 (CNA) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Fuente: NIST NVD | Registro visto por primera vez en NIST NVD | |
| Monitoreo | Fuente: ENISA EUVD | Registro visto por primera vez en ENISA EUVD | |
| Divulgación | Evaluación SSVC | CISA-ADP · explotación ninguna | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Multiple WSO2 products that use the OAuth refresh token grant are affected. An attacker can use this flaw to keep obtaining access tokens for accounts that have been blocked, gaining unauthorized access to those accounts and their resources.
Descripción original del registro (WSO2)
The refresh token grant type in WSO2 products fails to re-validate account status before issuing new access tokens. This weakness allows an attacker to obtain valid access tokens for user accounts even after they have been blocked by the user store, bypassing account lockout mechanisms. This vulnerability can lead to unauthorized access to user accounts and their associated resources. Attackers can leverage this to perform actions on behalf of blocked users, potentially leading to privilege escalation or data exfiltration depending on the permissions of the compromised account.
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
WSO2 API Manager |
Corregida | 3.1.0.308, 3.2.0.429, 3.2.1.49, 4.0.0.315, 4.1.0.214, 4.2.0.149, 4.3.0.62, 4.4.0.25, 4.5.0.9 | — | — |
WSO2 Universal Gateway |
Corregida | 4.5.0.9 | — | — |
WSO2 Traffic Manager |
Corregida | 4.5.0.9 | — | — |
WSO2 API Control Plane |
Corregida | 4.5.0.10 | — | — |
WSO2 Identity Server as Key Manager |
Corregida | 5.10.0.324 | — | — |
WSO2 Identity Server |
Corregida | 5.10.0.331, 5.11.0.376, 6.0.0.219, 6.1.0.205, 7.0.0.73 | — | — |
WSO2 Open Banking AM |
Corregida | 2.0.0.357 | — | — |
WSO2 Open Banking IAM |
Corregida | 2.0.0.377 | — | — |
WSO2 Carbon OAuth |
Corregida | 6.4.2.148, 6.4.111.122, 6.4.176.26, 6.4.180.10, 6.8.0.44, 6.9.6.21, 6.11.21.64, 6.13.16.13, 6.13.19.7, 6.13.27.1, 7.0.26.37 | — | — |
2.0.0.3572.0.0.3773.1.0.3083.2.0.4293.2.1.494.0.0.3154.1.0.2144.2.0.1494.3.0.624.4.0.254.5.0.94.5.0.105.10.0.3245.10.0.3315.11.0.3766.0.0.2196.1.0.2056.4.2.1486.4.111.1226.4.176.266.4.180.106.8.0.446.9.6.216.11.21.646.13.16.136.13.19.76.13.27.17.0.0.737.0.26.37Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3676/Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
