Incorrect Authorization in Multiple WSO2 Products Allows API Access via Refresh Token
WSO2 API Manager · WSO2 Identity Server
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.wso2.am:am-parent Maven |
| No fix yet |
| org.wso2.is:identity-server-parent Maven |
|
WSO2 API Manager · WSO2 Identity Server
| Product | Affected | Fixed in |
|---|---|---|
| org.wso2.am:am-parent Maven |
| No fix yet |
| org.wso2.is:identity-server-parent Maven |
|
≥ 5.11.0-alpha · ≤ 5.11.0| No fix yet |
An incorrect authorization vulnerability exists in multiple WSO2 products, allowing protected APIs to be accessed directly using a refresh token instead of the expected access token. Due to improper authorization checks and token mapping, session cookies are not required for API access, potentially enabling unauthorized operations.
Exploitation requires an attacker to obtain a valid refresh token of an admin user. Since refresh tokens generally have a longer expiration time, this could lead to prolonged unauthorized access to API resources, impacting data confidentiality and integrity.
From the CVE record · WSO2
Incorrect authorization checks let protected APIs accept an admin user's valid refresh token instead of an access token, without requiring a session cookie. An attacker who obtains that token can access API resources and potentially perform unauthorized operations; the input does not specify any required user interaction.
Teams running WSO2 API Manager or WSO2 Identity Server should check the listed affected Maven package versions, from the specified prereleases through API Manager 4.0.0, 4.1.0 and 4.2.0, and Identity Server 5.11.0, 6.0.0 and 6.1.0.