GHSA-6qjp-wm6g-m32r WSO2 incorrect authorization vulnerability

• Maven org.wso2.am:am-parent: >= 4.2.0-beta, <= 4.2.0 (no fix yet) • Maven org.wso2.am:am-parent: >= 4.1.0-alpha, <= 4.1.0 (no fix yet) • Maven org.wso2.am:am-parent: >= 4.0.0-beta, <= 4.0.0 (no fix yet) • Maven org.wso2.is:identity-server-parent: >= 6.1.0-beta, <= 6.1.0 (no fix yet) • Maven org.wso2.is:identity-server-parent: >= 6.0.0-alpha3, <= 6.0.0 (no fix yet) • Maven org.wso2.is:identity-server-parent: >= 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.