SECURITY ADVISORY WSO2-2024-3573/CVE-2024-7096¶
Published: November 10, 2024
Version: 1.0.0
Severity: Medium
CVSS Score: 4.2 (CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N)
AFFECTED PRODUCTS¶
- WSO2 API Manager 4.3.0, 4.2.0, 4.1.0, 4.0.0, 3.2.1, 3.2.0, 3.1.0, 3.0.0, 2.6.0, 2.5.0, 2.2.0, 2.1.0, 2.0.0
- WSO2 Identity Server 7.0.0, 6.1.0, 6.0.0, 5.11.0, 5.10.0, 5.9.0, 5.8.0, 5.7.0, 5.6.0, 5.5.0, 5.4.1, 5.4.0, 5.3.0, 5.2.0
- WSO2 Identity Server as Key Manager 5.10.0, 5.9.0, 5.7.0, 5.6.0, 5.5.0, 5.3.0
- WSO2 Open Banking AM 2.0.0, 1.5.0, 1.4.0, 1.3.0
- WSO2 Open Banking KM 1.5.0, 1.4.0, 1.3.0
- WSO2 Open Banking IAM 2.0.0
Info
Please note that this announcement includes only the product versions affected as per our backporting policy.
OVERVIEW¶
Potential privilege escalation vulnerabilities via SOAP admin service.
DESCRIPTION¶
Due to a business logic error, a malicious actor can potentially create a new user with elevated permissions if the following conditions are met:
- SOAP admin services are accessible to the malicious actor.
- The deployment includes an attribute used for internal purposes, which is not included by default in WSO2 products.
- The deployment includes at least one custom role which has a permission that is not included by default in WSO2 Products.
- The malicious actor has knowledge of the custom role, and the attribute created in the deployment.
IMPACT¶
By exploiting this vulnerability, malicious actors may obtain higher privileges for self-registered users when prerequisites mentioned in the description section are met.
SOLUTION¶
Community Users (Open Source)¶
Apply the relevant fixes to your product using the public fix(es) provided below.
Commercial Users¶
Update your product to the specified update level—or a higher update level—to apply the fix.
Info
If you are a WSO2 customer with Support Subscription, please use WSO2 Updates in order to apply the fix.
Product Name | Product Version | U2 Update Level |
---|---|---|
wso2-obiam | 2.0.0 | 364 |
wso2-obam | 1.3.0 | 131 |
wso2-obam | 1.4.0 | 134 |
wso2-obam | 1.5.0 | 136 |
wso2-obam | 2.0.0 | 343 |
wso2am | 2.0.0 | 29 |
wso2am | 2.1.0 | 39 |
wso2am | 2.2.0 | 56 |
wso2am | 2.5.0 | 83 |
wso2am | 2.6.0 | 142 |
wso2am | 3.0.0 | 162 |
wso2am | 3.1.0 | 294 |
wso2am | 3.2.0 | 384 |
wso2am | 3.2.1 | 16 |
wso2am | 4.0.0 | 305 |
wso2am | 4.1.0 | 166 |
wso2am | 4.2.0 | 101 |
wso2am | 4.3.0 | 16 |
wso2is | 5.2.0 | 32 |
wso2is | 5.3.0 | 33 |
wso2is | 5.4.1 | 36 |
wso2is | 5.5.0 | 50 |
wso2is | 5.6.0 | 58 |
wso2is | 5.7.0 | 123 |
wso2is | 5.8.0 | 106 |
wso2is | 5.9.0 | 157 |
wso2is | 5.10.0 | 318 |
wso2is | 5.11.0 | 365 |
wso2is | 6.0.0 | 209 |
wso2is | 6.1.0 | 188 |
wso2is | 7.0.0 | 60 |
wso2is-km | 5.3.0 | 38 |
wso2is-km | 5.5.0 | 51 |
wso2is-km | 5.6.0 | 72 |
wso2is-km | 5.7.0 | 122 |
wso2is-km | 5.9.0 | 165 |
wso2is-km | 5.10.0 | 312 |
wso2-obkm | 1.3.0 | 114 |
wso2-obkm | 1.4.0 | 130 |
wso2-obkm | 1.5.0 | 120 |
For All Users¶
If applying the fix or update is not feasible, migrate to the latest unaffected version of the respective WSO2 product(s).