||
Skip to end of metadata
Go to start of metadata

Published: 08th October 2019

Severity: Low

CVSS Score: 3.5 (CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N)


AFFECTED PRODUCTS

WSO2 API Manager


OVERVIEW

A potential Reflected Cross-Site Scripting (XSS) vulnerability has been identified in the inline API documentation editor page of the API Publisher.

DESCRIPTION

A reflected XSS attack could be performed in the inline API documentation editor page of the API Publisher by sending an HTTP GET request with a harmful request parameter for 'docName'.


IMPACT

An attacker can trick a privileged user to click a crafted URL via email, IM or a neutral web site, then the attacker can make the browser to 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.

SOLUTION


Apply the following patch based on your product version by following the instructions in the README file. If you have any questions, post them to [email protected].

Please download the relevant patch based on the product you use following the matrix below. The patch can also be downloaded from http://wso2.com/security-patch-releases/.


Code

Product

Version

Patch

AM

WSO2 API Manager

2.6.0

WSO2-CARBON-PATCH-4.4.0-4941

Note: If you are a WSO2 customer with Support Subscription, please use WSO2 Update Manager (WUM) updates in order to apply the fix. This patch is intended for WSO2 community (free) users.


NOTES

If you are using newer versions of affected products than the ones mentioned in the “SOLUTION” section, this vulnerability is fixed. 

It is highly recommended to migrate older versions of the WSO2 products to the latest released version to receive security fixes.


CREDITS

WSO2 thanks, Sathish Kumar Balakrishnan (Cyber Security Works Pvt Ltd) for responsibly reporting the identified issue and working with us as we addressed them.


  • No labels