Skip to main content
← All vulnerabilities
CVE-2024-2321GHSA-6QJP-WM6G-M32R

Incorrect Authorization in Multiple WSO2 Products Allows API Access via Refresh Token

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 4.0.0.275, 4.1.0.153, 4.2.0.83, 5.11.0.326, 6.0.0.172, and 1 more
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

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.

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  3. Record last updated

Affected versions

  • WSO2 WSO2 API Manager

    From 4.0.0 · fixed in 4.0.0.275; From 4.1.0 · fixed in 4.1.0.153; From 4.2.0 · fixed in 4.2.0.83

  • WSO2 WSO2 Identity Server

    From 5.11.0 · fixed in 5.11.0.326; From 6.0.0 · fixed in 6.0.0.172; From 6.1.0 · fixed in 6.1.0.130

  • org.wso2.am:am-parentMaven

    From 4.2.0-beta · through 4.2.0

  • org.wso2.am:am-parentMaven

    From 4.1.0-alpha · through 4.1.0

  • org.wso2.am:am-parentMaven

    From 4.0.0-beta · through 4.0.0

  • org.wso2.is:identity-server-parentMaven

    From 6.1.0-beta · through 6.1.0

  • org.wso2.is:identity-server-parentMaven

    From 6.0.0-alpha3 · through 6.0.0

  • org.wso2.is:identity-server-parentMaven

    From 5.11.0-alpha · through 5.11.0

References 1

security.docs.wso2.com