SECURITY ADVISORY WSO2-2024-3566/CVE-2024-7074¶
Published: November 10, 2024
Version: 1.0.0
Severity: Medium
CVSS Score: 6.8 (CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H)
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 Enterprise Integrator 6.6.0, 6.5.0, 6.4.0, 6.3.0, 6.2.0, 6.1.1, 6.1.0, 6.0.0
- WSO2 Enterprise Service Bus 5.0.0, 4.9.0
- WSO2 Micro Integrator 1.0.0
- WSO2 Open Banking AM 2.0.0, 1.5.0, 1.4.0, 1.3.0
Info
Please note that this announcement includes only the product versions affected as per our backporting policy.
OVERVIEW¶
Authenticated arbitrary file upload via SOAP admin service.
DESCRIPTION¶
Due to improper validation of user input, a malicious actor could upload an arbitrary file to a user controlled location of the server. By leveraging the arbitrary file upload vulnerability, it is further possible to gain remote code execution on the server. However, malicious actors require admin privileges to exploit this vulnerability
IMPACT¶
By leveraging the vulnerability, a malicious actor with admin privileges may perform remote code execution by uploading a specially crafted payload.
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 |
|---|---|---|
| wso2ei | 6.0.0 | 21 |
| wso2ei | 6.1.0 | 38 |
| wso2ei | 6.1.1 | 42 |
| wso2ei | 6.2.0 | 61 |
| wso2ei | 6.3.0 | 69 |
| wso2ei | 6.4.0 | 96 |
| wso2ei | 6.5.0 | 102 |
| wso2ei | 6.6.0 | 198 |
| wso2am | 2.0.0 | 28 |
| wso2am | 2.1.0 | 38 |
| wso2am | 2.2.0 | 57 |
| wso2am | 2.5.0 | 83 |
| wso2am | 2.6.0 | 143 |
| wso2am | 3.0.0 | 162 |
| wso2am | 3.1.0 | 293 |
| wso2am | 3.2.0 | 384 |
| wso2am | 3.2.1 | 16 |
| wso2am | 4.0.0 | 305 |
| wso2am | 4.1.0 | 166 |
| wso2am | 4.2.0 | 100 |
| wso2am | 4.3.0 | 16 |
| wso2esb | 4.9.0 | 10 |
| wso2esb | 5.0.0 | 28 |
| wso2emm | 2.2.0 | 27 |
| wso2mi | 1.0.0 | 49 |
| wso2-obam | 1.3.0 | 132 |
| wso2-obam | 1.4.0 | 135 |
| wso2-obam | 1.5.0 | 137 |
| wso2-obam | 2.0.0 | 342 |
For All Users¶
If applying the fix or update is not feasible, migrate to the latest unaffected version of the respective WSO2 product(s).
CREDITS¶
WSO2 thanks, Anonymous working with Trend Micro Zero Day Initiative for responsibly reporting the identified issue and working with us as we addressed it.