SECURITY ADVISORY WSO2-2024-3450/CVE-2024-5848¶
Published: November 10, 2024
Version: 1.0.0
Severity: Medium
CVSS Score: 6.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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
- WSO2 Open Banking AM : 2.0.0
Info
Please note that this announcement includes only the product versions affected as per our backporting policy.
OVERVIEW¶
Reflected Cross Site Scripting (XSS) vulnerability.
DESCRIPTION¶
Due to lack of validation, user supplies data directly pass into the server response of a vulnerable services endpoint, without any sanitization or encoding.
IMPACT¶
By leveraging the XSS attack, a malicious actor can make the browser get redirected to a malicious website, make changes in the UI of the web page, retrieve information from the browser or harm otherwise. However, since all the session related sensitive cookies are set with httpOnly flag and protected, session hijacking or similar attacks would not be possible. However, if the service endpoint is not permitted at the gateway level, the impact would be further reduced.
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-obam | 2.0.0 | 349 |
wso2am | 3.1.0 | 285 |
wso2am | 3.2.0 | 375 |
wso2am | 3.2.1 | 10 |
wso2am | 4.0.0 | 300 |
wso2am | 4.1.0 | 160 |
wso2am | 4.2.0 | 92 |
wso2am | 4.3.0 | 10 |
For All Users¶
If applying the fix or update is not feasible, migrate to the latest unaffected version of the respective WSO2 product(s).
In addition, apply the given configuration below to the _OpenService_.xml
file located in <APIM_HOME>/repository/deployment/server/synapse-configs/default/api/
if the file does not contain them after the update.
<inSequence>
<class name="org.wso2.carbon.apimgt.gateway.mediators BotDetectionMediator"/>
<property name="messageType" value="text/plain" scope="axis2" type="STRING"/>
<property name="NO_ENTITY_BODY" value="true" scope="axis2" type="BOOLEAN"/>
<respond/>
</inSequence>