Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Published:  08-31-31st August 2016

 


OVERVIEW

Following four scenarios were found to be vulnerable to XML Signature Wrapping (XSW) attacks, in the WSO2 platform:

...

None of the external applications (e.g: Google Apps, Salesforce) using WSO2 Identity Server as the SAML 2.0 or WS-Federation Identity Provider are vulnerable to this attack.

 


DESCRIPTION

In order to preserve the integrity of the SAML assertion and response sent by the SAML Identity Provider to the Service Provider (relying party), XML signatures are used. The relying party can validate the signature of the assertion and response for ensuring that the original message is not altered. In XML Signature Wrapping attacks, the structure of the message is altered such that the relying party can be tricked when it parses the XML message.

The attacker should possess a valid SAML token in hand for wrapping the signature and forwarding to the relying party. Therefore the attacker must be an internal user of the organization who already possesses a valid user account in the system.

 


IMPACT

Through a successful exploit of the vulnerability, the attacker would be able to impersonate a user and gain access to the SAML SSO consumer applications that the victim is authorized.

However the attack would only be possible where the WSO2 products act as the SAML consumer (e.g. API Manager Store/Publisher, Identity Server Dashboard). Other SAML relying party websites/applications that use WSO2 Identity Server as an Identity Provider have no impact from this attack.

 


SOLUTION

After applying below patches, WSO2 products correctly validate SAML responses and assertions in SAML consumer applications and avoid possible XML Signature Wrapping (XSW) attacks.

Apply the following patches based on your products by following the instructions in the README file.

if you have any questions, post them to security@wso2.com

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


 

Code

Product

Version

Patch

APIM

WSO2 API Manager

2.0.0

WSO2-CARBON-PATCH-4.4.0-0327    

WSO2-CARBON-PATCH-4.4.0-0365

WSO2-CARBON-PATCH-4.4.0-0366

APIM Analytics

WSO2 API Manager Analytics

2.0.0

WSO2-CARBON-PATCH-4.4.0-0366

APPM

WSO2 App Manager

1.2.0

WSO2-CARBON-PATCH-4.4.0-0326

WSO2-CARBON-PATCH-4.4.0-0327

WSO2-CARBON-PATCH-4.4.0-0365

WSO2-CARBON-PATCH-4.4.0-0339

AS

WSO2 Application Server

5.3.0

WSO2-CARBON-PATCH-4.4.0-0354

WSO2-CARBON-PATCH-4.4.0-0347

BPS

WSO2 Business Process Server

3.5.1

WSO2-CARBON-PATCH-4.4.0-0352

BRS

WSO2 Business Rules Server

2.2.0

WSO2-CARBON-PATCH-4.4.0-0329

CEP

WSO2 Complex Event Processor

4.1.0

WSO2-CARBON-PATCH-4.4.0-0329

DAS

WSO2 Data Analytics Server

3.0.1

WSO2-CARBON-PATCH-4.4.0-0329

WSO2-CARBON-PATCH-4.4.0-0348

DS

WSO2 Dashboard Server

2.0.0

WSO2-CARBON-PATCH-4.4.0-0329

WSO2-CARBON-PATCH-4.4.0-0331

WSO2-CARBON-PATCH-4.4.0-0355

WSO2-CARBON-PATCH-4.4.0-0340

DSS

WSO2 Data Services Server

3.5.0

WSO2-CARBON-PATCH-4.4.0-0353

EMM

WSO2 Enterprise Mobility Manager

2.0.1

WSO2-CARBON-PATCH-4.4.0-0329

WSO2-CARBON-PATCH-4.4.0-0331

WSO2-CARBON-PATCH-4.4.0-0355

WSO2-CARBON-PATCH-4.4.0-0358

IS

WSO2 Identity Server

5.1.0

WSO2-CARBON-PATCH-4.4.0-0329

WSO2-CARBON-PATCH-4.4.0-0331

WSO2-CARBON-PATCH-4.4.0-0355

MB

WSO2 Message Broker

3.1.0

WSO2-CARBON-PATCH-4.4.0-0353

ML

WSO2 Machine Learner

1.1.0

WSO2-CARBON-PATCH-4.4.0-0353

 


NOTES

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