CVE-2024-2321
WSO2 incorrect authorization vulnerability
Overview
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.
Source: OX vulnerability database
Severity
5.6 · MEDIUM
CVSS 3.1 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
Weakness: CWE-863
Affected packages · 2
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| Maven | org.wso2.am:am-parent | >=4.2.0-beta, <=4.2.0>=4.1.0-alpha, <=4.1.0>=4.0.0-beta, <=4.0.0 | No fix yet |
| Maven | org.wso2.is:identity-server-parent | >=6.1.0-beta, <=6.1.0>=6.0.0-alpha3, <=6.0.0>=5.11.0-alpha, <=5.11.0 | No fix yet |
Open a package to see all its vulnerabilities.
Operating systems
No Linux distribution reports this ID.
References
- github.com https://github.com/wso2/docs-security/blob/76bad9a2f38dc3377af476d0be52c6e775e3d864/en/docs/security-announcements/security-advisories/2024/WSO2-2024-3213.md
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2024-2321
- security.docs.wso2.com https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2024/WSO2-2024-3213
- security.docs.wso2.com https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2024/WSO2-2024-3213/
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.