Improper Token Renewal in Refresh Token Grant in Multiple WSO2 Products Allows Unauthorized Access to Blocked Accounts
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.1.0.308, 3.2.0.429, 3.2.1.49, 4.0.0.315, 4.1.0.214, and 24 more
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.1.0.308, 3.2.0.429, 3.2.1.49, 4.0.0.315, 4.1.0.214, or one of 24 more.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 8/100 · provisional
- Fix
- Fixed in 3.1.0.308, 3.2.0.429, 3.2.1.49, 4.0.0.315, 4.1.0.214, and 24 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Read the original description
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.
What to do
Upgrade to a fixed version: 3.1.0.308, 3.2.0.429, 3.2.1.49, 4.0.0.315, 4.1.0.214, or one of 24 more.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- WSO2 WSO2 API Manager
From 3.1.0 · fixed in 3.1.0.308; From 3.2.0 · fixed in 3.2.0.429; From 3.2.1 · fixed in 3.2.1.49; From 4.0.0 · fixed in 4.0.0.315; From 4.1.0 · fixed in 4.1.0.214; From 4.2.0 · fixed in 4.2.0.149; From 4.3.0 · fixed in 4.3.0.62; From 4.4.0 · fixed in 4.4.0.25; From 4.5.0 · fixed in 4.5.0.9
- WSO2 WSO2 Universal Gateway
From 4.5.0 · fixed in 4.5.0.9
- WSO2 WSO2 Traffic Manager
From 4.5.0 · fixed in 4.5.0.9
- WSO2 WSO2 API Control Plane
From 4.5.0 · fixed in 4.5.0.10
- WSO2 WSO2 Identity Server as Key Manager
From 5.10.0 · fixed in 5.10.0.324
- WSO2 WSO2 Identity Server
From 5.10.0 · fixed in 5.10.0.331; From 5.11.0 · fixed in 5.11.0.376; From 6.0.0 · fixed in 6.0.0.219; From 6.1.0 · fixed in 6.1.0.205; From 7.0.0 · fixed in 7.0.0.73
- WSO2 WSO2 Open Banking AM
From 2.0.0 · fixed in 2.0.0.357
- WSO2 WSO2 Open Banking IAM
From 2.0.0 · fixed in 2.0.0.377
- org.wso2.carbon.identity.inbound.auth.oauth2:org.wso2.carbon.identity.oauth
From 6.4.2 · fixed in 6.4.2.148; From 6.4.111 · fixed in 6.4.111.122; From 6.4.176 · fixed in 6.4.176.26; From 6.4.180 · fixed in 6.4.180.10; From 6.8.0 · fixed in 6.8.0.44; From 6.9.6 · fixed in 6.9.6.21; From 6.11.21 · fixed in 6.11.21.64; From 6.13.16 · fixed in 6.13.16.13; From 6.13.19 · fixed in 6.13.19.7; From 6.13.27 · fixed in 6.13.27.1; From 7.0.26 · fixed in 7.0.26.37
Evidence 1
- Advisory
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.