Skip to content

WSO2 incorrect authorization vulnerability

Moderate severity GitHub Reviewed Published Feb 27, 2025 to the GitHub Advisory Database • Updated Mar 3, 2025

Package

maven org.wso2.am:am-parent (Maven)

Affected versions

>= 4.2.0-beta, <= 4.2.0
>= 4.1.0-alpha, <= 4.1.0
>= 4.0.0-beta, <= 4.0.0

Patched versions

None
maven org.wso2.is:identity-server-parent (Maven)
>= 6.1.0-beta, <= 6.1.0
>= 6.0.0-alpha3, <= 6.0.0
>= 5.11.0-alpha, <= 5.11.0
None

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.

References

Published by the National Vulnerability Database Feb 27, 2025
Published to the GitHub Advisory Database Feb 27, 2025
Reviewed Mar 3, 2025
Last updated Mar 3, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(12th percentile)

Weaknesses

CVE ID

CVE-2024-2321

GHSA ID

GHSA-6qjp-wm6g-m32r

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.