NetSight
medium4.9

CVE-2024-9517

Improper Token Renewal in Refresh Token Grant in Multiple WSO2 Products Allows Unauthorized Access to Blocked Accounts

Impact

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.

An attacker can exploit this over the network, with a regular user account, without any action by a user. Specific conditions have to be met, which makes an attack harder. If it succeeds: low risk of data being read, low risk of data or systems being changed. The attack can reach beyond the vulnerable component itself.

Affected products · WSO2

ProductAffected versions
WSO2 API Control Plane
from 4.5.0 before 4.5.0.10
WSO2 API Manager
from 3.1.0 before 3.1.0.308
from 3.2.0 before 3.2.0.429
from 3.2.1 before 3.2.1.49
from 4.0.0 before 4.0.0.315
from 4.1.0 before 4.1.0.214
from 4.2.0 before 4.2.0.149
WSO2 Carbon OAuth
from 6.4.2 before 6.4.2.148
from 6.4.111 before 6.4.111.122
from 6.4.176 before 6.4.176.26
from 6.4.180 before 6.4.180.10
from 6.8.0 before 6.8.0.44
from 6.9.6 before 6.9.6.21
WSO2 Identity Server
from 5.10.0 before 5.10.0.331
from 5.11.0 before 5.11.0.376
from 6.0.0 before 6.0.0.219
from 6.1.0 before 6.1.0.205
from 7.0.0 before 7.0.0.73
WSO2 Identity Server as Key Manager
from 5.10.0 before 5.10.0.324
WSO2 Open Banking AM
from 2.0.0 before 2.0.0.357
WSO2 Open Banking IAM
from 2.0.0 before 2.0.0.377
WSO2 Traffic Manager
from 4.5.0 before 4.5.0.9
WSO2 Universal Gateway
from 4.5.0 before 4.5.0.9

Weakness classification

References