Security Advisory WSO2-2017-0257

Published: September 04, 2017

Severity: Low

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


AFFECTED PRODUCTS

  • WSO2 Application Server 5.3.0
  • WSO2 Business Process Server 3.6.0
  • WSO2 Business Rules Server 2.2.0
  • WSO2 Complex Event Processor 4.2.0
  • WSO2 Dashboard Server 2.0.0
  • WSO2 Data Analytics Server 3.1.0
  • WSO2 Data Services Server 3.5.1
  • WSO2 Machine Learner 1.2.0

OVERVIEW

A potential Stored Cross Site Scripting (XSS) vulnerability is detected in a JavaScript utility used for displaying messages in the Management Console.

DESCRIPTION

A stored XSS attack could be performed in the Management Console by filling a form field with a harmful script and later executing it when trying to perform a UI action based on that data.

This has been possible due to the utility JavaScript function used to display the pop messages related to that UI action not being properly encoded to prevent XSS.

IMPACT

By performing a Stored XSS attack, an attacker 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 attack would not be possible.

SOLUTION

Apply the following patches based on your product version by following the instructions in the README file. If you have any questions, post them to security@wso2.com.

Download the relevant patches based on the products you use following the matrix below. Patches can also be downloaded from Security Patch Releases.

Code Product Version Patch
AS WSO2 Application Server 5.3.0
BRS WSO2 Business Rules Server 2.2.0
CEP WSO2 Complex Event Processor 4.2.0
DS WSO2 Dashboard Server 2.0.0
DAS WSO2 Data Analytics Server 3.1.0
DSS WSO2 Data Services Server 3.5.1
ML WSO2 Machine Learner 1.2.0
BPS WSO2 Business Process Server 3.6.0

Info

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