Skip to content
Medium 4.9

The refresh token grant type in WSO2 products fails to re-validate account status before issuing...

CVE-2024-9517 First seen on SecPulse

Affected packages

EcosystemPackageAffectedFixed
WSO2 WSO2 API Manager
≥ 3.1.0, < 3.1.0.308
≥ 3.2.0, < 3.2.0.429
≥ 3.2.1, < 3.2.1.49
≥ 4.0.0, < 4.0.0.315
≥ 4.1.0, < 4.1.0.214
≥ 4.2.0, < 4.2.0.149
+3 more
3.1.0.308
3.2.0.429
3.2.1.49
4.0.0.315
4.1.0.214
4.2.0.149
WSO2 WSO2 Universal Gateway
≥ 4.5.0, < 4.5.0.9
4.5.0.9
WSO2 WSO2 Traffic Manager
≥ 4.5.0, < 4.5.0.9
4.5.0.9
WSO2 WSO2 API Control Plane
≥ 4.5.0, < 4.5.0.10
4.5.0.10
WSO2 WSO2 Identity Server as Key Manager
≥ 5.10.0, < 5.10.0.324
5.10.0.324
WSO2 WSO2 Identity Server
≥ 5.10.0, < 5.10.0.331
≥ 5.11.0, < 5.11.0.376
≥ 6.0.0, < 6.0.0.219
≥ 6.1.0, < 6.1.0.205
≥ 7.0.0, < 7.0.0.73
5.10.0.331
5.11.0.376
6.0.0.219
6.1.0.205
7.0.0.73
WSO2 WSO2 Open Banking AM
≥ 2.0.0, < 2.0.0.357
2.0.0.357
WSO2 WSO2 Open Banking IAM
≥ 2.0.0, < 2.0.0.377
2.0.0.377
WSO2 WSO2 Carbon OAuth
≥ 6.4.2, < 6.4.2.148
≥ 6.4.111, < 6.4.111.122
≥ 6.4.176, < 6.4.176.26
≥ 6.4.180, < 6.4.180.10
≥ 6.8.0, < 6.8.0.44
≥ 6.9.6, < 6.9.6.21
+5 more
6.4.2.148
6.4.111.122
6.4.176.26
6.4.180.10
6.8.0.44
6.9.6.21
Original description The description as published by the source.

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.

Source: CVE.org (CVE Program・cvelistV5) NVD GitHub Advisory

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details