Security Patch Releases

API Manager

<< All Products

Security PatchProduct VersionDescription
WSO2-CARBON-PATCH-4.4.0-16642.1.0Release Date - Dec 19, 2017

With the Apache Tomcat upgrade, following Common Vulnerability Exposure is fixed. CVE-2017-12616: Information Disclosure

Security Advisory Link
WSO2-CARBON-PATCH-4.4.0-11582.1.0Release Date - Sep 4, 2017

With the Apache Tomcat upgrade, following Common Vulnerability Exposure is fixed. CVE-2017-5647: Information Disclosure

Security Advisory Link
WSO2-CARBON-PATCH-4.4.0-11152.1.0Release Date - Sep 4, 2017

In Carbon Tenant Management UI, the identified XSS attack can be performed when a user injects a malicious executable script as a user input through carbon management console. This issue has been fixed in affected component versions with security patch/update given for specific products.

Security Advisory Link
WSO2-CARBON-PATCH-4.4.0-12322.1.0Release Date - Sep 4, 2017

This addresses a potential XSS vulnerability identified in Dashboard Portal login-controller when Single Sign On is enabled. It has been identified that two such parameters displayed in the HTML page result were not properly encoded before displaying

Security Advisory Link
WSO2-CARBON-PATCH-4.4.0-13102.1.0Release Date - Sep 4, 2017

A reflected XSS attack could be performed in the Registry Browser of the Management Console by sending an HTTP GET request with a harmful request parameter.

Security Advisory Link
WSO2-CARBON-PATCH-4.4.0-14112.1.0Release Date - Sep 4, 2017

WSO2 API Manager uses "Double Submit Cookie" mechanism for CSRF protection. It has been found that the generated CSRF cookie's expiry is not explicitly set which results in expiring the cookie after generation. This results in setting the associated HTTP header with a null value, which leads to a CSRF vulnerability.

Security Advisory Link
WSO2-CARBON-PATCH-4.4.0-14232.1.0Release Date - Sep 4, 2017

This vulnerability is discovered in the message dialog page of the Management Console. However, exploiting the vulnerability remotely is not possible as the malicious script should be injected to an input and given input should be displayed back to the user in a message dialog box.

Security Advisory Link
WSO2-CARBON-PATCH-4.4.0-09132.1.0Release Date - Apr 30, 2017

Management Console is vulnerable to a potential sensitive data exposure vulnerability through the advanced search option

Security Advisory Link
WSO2-CARBON-PATCH-4.4.0-08672.1.0Release Date - Apr 30, 2017

The tenant creation page of WSO2 products auto completes the passwords in the user’s web browser when the password is stored in the browser.

Security Advisory Link
WSO2-CARBON-PATCH-4.4.0-10241.2.0Release Date - Apr 30, 2017

Management Console is vulnerable to a potential authentication bypass vulnerability that let's attackers view a restricted web page.

Security Advisory Link
Update via WSO2 Update Manager2.0.0Release Date - Nov 8, 2016

WSO2 API Manager provides an API for swagger definition import by swagger resource url. This particular API is vulnerable for unauthorized user access and it can be invoked by anonymous users. Thus an attacker who doesn’t even have credentials to access API Publisher, can possibly access the swagger definition url import API.

Security Advisory Link
Update via WSO2 Update Manager2.0.0Release Date - Nov 8, 2016

An attacker with access to the WSO2 Management Console can input a malicious XXE script in the try-it tool UI menu or can directly attack with xml input and disclose any file located in the file system. The reflected and stored XSS vulnerabilities allow deployment of malicious code in the application by means of providing specifically crafted url to a user.

Security Advisory Link
Update via WSO2 Update Manager2.0.0Release Date - Nov 8, 2016

When a user browses a page where it contains some sensitive data and logout from the management console, still users can go back (by using browser’s Back button) and view that page without login due to browser cache.

Security Advisory Link
Update via WSO2 Update Manager2.0.0Release Date - Nov 8, 2016

According to http://www.securityfocus.com/bid/58536/info, H2 database versions prior to 1.3.171 are vulnerable to Remote Security Bypass Vulnerability.

Security Advisory Link
Update via WSO2 Update Manager2.0.0Release Date - Nov 8, 2016

Following pages in the management console were found to be vulnerable to open redirect attacks, in the products mentioned here. - XACML Policy Administration - Identity Provider Management - Workflow Management - User Management An attacker can possibly attack the above UI components, by modifying some query parameters that contain a URL value in management console context. They can modify the respective query parameter value such that the management console will redirect the request to the specified URL.

Security Advisory Link
WSO2-CARBON-PATCH-4.4.0-04202.0.0Release Date - Sep 30, 2016

XSS vulnerabilities were discovered in the Message Flows component. An attacker can possibly attack the management console, via that component, using reflected XSS. He can inject malicious scripts as a part of the URL which will be reflected in that component's pages.

Security Advisory Link
WSO2-CARBON-PATCH-4.4.0-03982.0.0Release Date - Sep 30, 2016

Error responses returned by the WSO2 API Manager were discovered to be vulnerable to XSS attack, the requests made to an API with resource paths containing invalid contexts/resource names/methods that are made of malicious scripts could result in reflected XSS attacks.

Security Advisory Link
WSO2-CARBON-PATCH-4.4.0-03702.0.0Release Date - Sep 30, 2016

Carbon Metrics component of WSO2 Products are discovered to be vulnerable to XSS attacks, an attacker can possibly attack the management console, via that component, using reflected XSS. He can inject malicious scripts as a part of the URL which will be reflected in that component's pages.

Security Advisory Link
WSO2-CARBON-PATCH-4.4.0-03662.0.0Release Date - Aug 31, 2016

Preventing possible XML Signature Wrapping (XSW) attacks in SAML 2.0 based Single Sign On (SSO) flow, SAML 2.0 bearer grant type for OAuth token exchange and in SAML 2.0 federated authentication flow.

Security Advisory Link
WSO2-CARBON-PATCH-4.4.0-03652.0.0Release Date - Aug 31, 2016

Preventing possible XML Signature Wrapping (XSW) attacks in SAML 2.0 based Single Sign On (SSO) flow, SAML 2.0 bearer grant type for OAuth token exchange and in SAML 2.0 federated authentication flow.

Security Advisory Link
WSO2-CARBON-PATCH-4.4.0-03272.0.0Release Date - Aug 31, 2016

Preventing possible XML Signature Wrapping (XSW) attacks in SAML 2.0 based Single Sign On (SSO) flow, SAML 2.0 bearer grant type for OAuth token exchange and in SAML 2.0 federated authentication flow.

Security Advisory Link
WSO2-CARBON-PATCH-4.4.0-00841.10.0Release Date - May 24, 2016

WSO2 API Manager, Publisher application's documentation link section is vulnerable to Cross Site Scripting (XSS), which affects documentation section of WSO2 API Manager, Store application as well. Swagger UI component of WSO2 API Manager Store application is vulnerable to XSS as well. In addition API Manager, Store and Publisher applications does not renew session ID upon user login, resulting in possibility to perform Session Fixation attack.
WSO2-CARBON-PATCH-4.2.0-18261.5.0Release Date - May 9, 2016

A user with "/permission/admin/monitor/logging" permission can read any file in the filesystem via getLineNumbers and getLogLinesFromFile operations in LogViewer admin service. The request to the admin service accepts a file path relative to the carbon log file directory (i.e. /repositories/logs), hence can access any file in the file system.
WSO2-CARBON-PATCH-4.2.0-18251.6.0 / 1.7.0 / 1.8.0 / 1.9.0 / 1.9.1Release Date - May 9, 2016

A user with "/permission/admin/monitor/logging" permission can read any file in the filesystem via getLineNumbers and getLogLinesFromFile operations in LogViewer admin service. The request to the admin service accepts a file path relative to the carbon log file directory (i.e. /repositories/logs), hence can access any file in the file system.
WSO2-CARBON-PATCH-4.4.0-01761.10.0Release Date - May 9, 2016

A user with "/permission/admin/monitor/logging" permission can read any file in the filesystem via getLineNumbers and getLogLinesFromFile operations in LogViewer admin service. The request to the admin service accepts a file path relative to the carbon log file directory (i.e. /repositories/logs), hence can access any file in the file system.
WSO2-CARBON-PATCH-4.4.0-00441.10.0Release Date - Jan 15, 2016

Due to a vulnerability discovered in the WSO2 authentication module, server admin services can be invoked cross-tenant, given that the following criteria is met.

1. The tenant corresponding to the admin service must have the same username of the invoker (the attacker).
2. Invoker and the admin service belong to two tenants.
3. The tenant corresponding to the admin service must have the right level permissions to the user in its user store with the same username as of the invoker (attacker).
4. The attacker must be a valid user in any tenant.
WSO2-CARBON-PATCH-4.2.0-16991.9.1 / 1.9.0 / 1.8.0 / 1.7.0 / 1.6.0 / 1.5.0Release Date - Jan 15, 2016

Due to a vulnerability discovered in the WSO2 authentication module, server admin services can be invoked cross-tenant, given that the following criteria is met.

1. The tenant corresponding to the admin service must have the same username of the invoker (the attacker).
2. Invoker and the admin service belong to two tenants.
3. The tenant corresponding to the admin service must have the right level permissions to the user in its user store with the same username as of the invoker (attacker).
4. The attacker must be a valid user in any tenant.
WSO2-CARBON-PATCH-4.0.0-06671.1.1Release Date - Jan 15, 2016

Due to a vulnerability discovered in the WSO2 authentication module, server admin services can be invoked cross-tenant, given that the following criteria is met.

1. The tenant corresponding to the admin service must have the same username of the invoker (the attacker).
2. Invoker and the admin service belong to two tenants.
3. The tenant corresponding to the admin service must have the right level permissions to the user in its user store with the same username as of the invoker (attacker).
4. The attacker must be a valid user in any tenant.
WSO2-CARBON-PATCH-4.0.0-06641.0.0Release Date - Jan 15, 2016

Due to a vulnerability discovered in the WSO2 authentication module, server admin services can be invoked cross-tenant, given that the following criteria is met.

1. The tenant corresponding to the admin service must have the same username of the invoker (the attacker).
2. Invoker and the admin service belong to two tenants.
3. The tenant corresponding to the admin service must have the right level permissions to the user in its user store with the same username as of the invoker (attacker).
4. The attacker must be a valid user in any tenant.
WSO2-CARBON-PATCH-4.2.0-09551.8.0 / 1.7.0 / 1.6.0Release Date - Dec 11, 2015

WSO2 products based on Carbon 4.2.0, using Tomcat version 7.0.34 are vulnerable to a security threat identified as Request Smuggling. According to the Tomcat Security Team, this vulnerability allows attackers to craft a malformed chunk as part of a chucked request, causing Tomcat to read part of the request body as a new request.
WSO2-CARBON-PATCH-4.2.0-11541.5.0Release Date - Dec 11, 2015

WSO2 products based on Carbon 4.2.0, using Tomcat version 7.0.34 are vulnerable to a security threat identified as Request Smuggling. According to the Tomcat Security Team, this vulnerability allows attackers to craft a malformed chunk as part of a chucked request, causing Tomcat to read part of the request body as a new request.
WSO2-CARBON-PATCH-4.2.0-12611.9.1 / 1.9.0 / 1.8.0 / 1.7.0 / 1.6.0 / 1.5.0Release Date - Dec 11, 2015

WSO2 products based on Carbon 4.2.0, using Tomcat version 7.0.34 are vulnerable to a security threat identified as Request Smuggling. According to the Tomcat Security Team, this vulnerability allows attackers to craft a malformed chunk as part of a chucked request, causing Tomcat to read part of the request body as a new request.
WSO2-CARBON-PATCH-4.2.0-12621.8.0 / 1.7.0 / 1.6.0Release Date - Dec 11, 2015

WSO2 products based on Carbon 4.2.0, using Tomcat version 7.0.34 are vulnerable to a security threat identified as Request Smuggling. According to the Tomcat Security Team, this vulnerability allows attackers to craft a malformed chunk as part of a chucked request, causing Tomcat to read part of the request body as a new request.
WSO2-CARBON-PATCH-4.0.0-06611.0.0Release Date - Nov 25, 2015

The Apache Commons Collections (ACC) library is vulnerable to insecure deserialization of data, which may result in arbitrary code execution. Java applications that either directly use ACC, or contain ACC in their classpath, may be vulnerable to arbitrary code execution. All WSO2 products ship with the Apache Commons Collections library. More information on how to exploit the vulnerability in detail, can be found from here
WSO2-CARBON-PATCH-4.2.0-16361.9.1 / 1.9.0 / 1.8.0 / 1.7.0 / 1.6.0 / 1.5.0Release Date - Nov 5, 2015

The Apache Commons Collections (ACC) library is vulnerable to insecure deserialization of data, which may result in arbitrary code execution. Java applications that either directly use ACC, or contain ACC in their classpath, may be vulnerable to arbitrary code execution. All WSO2 products ship with the Apache Commons Collections library. More information on how to exploit the vulnerability in detail, can be found from here
WSO2-CARBON-PATCH-4.2.0-14641.9.1 / 1.9.0 / 1.8.0 / 1.7.0 / 1.6.0 / 1.5.0Release Date - Sep 11, 2015

WSO2 products based on Kernel Version 4.1.0 are vulnerable to XSS and CSRF attacks. XSS enables attackers to inject client-side script into web pages viewed by other users, while CSRF forces an end user to execute unwanted actions on a web application to which they are currently authenticated. This vulnerability allows attackers to bypass access controls, such as the same-origin policy and malicious exploitation of a website, where unauthorized commands are transmitted from a user that the website trusts.
WSO2-CARBON-PATCH-4.2.0-10951.9.1 / 1.9.0 / 1.8.0 / 1.7.0 / 1.6.0 / 1.5.0Release Date - Jun 3, 2015

In light of the prevailing vulnerability of Apache WSS4J to Bleichenbacher attacks, we have identified a vulnerability in WSO2 Carbon 4.2.0 products that use WS-Security features from the Apache WSS4J library. Of a number of attacks on PKCS#1 v1.5 Key Transport Algorithm - used to encrypt symmetric keys as part of WS-Security - one attack exploits the ability for WSS4J to leak information on where particular decryption operations fail. This vulnerability has been fixed by generating a new symmetric key, so that the attacker would not be able to find out if the failure was due to decrypting the key or the data. However, it is still possible for attackers to craft a message in order to find out where the decryption failure took place, again leaving WSS4J vulnerable to the original attack. In Apache WSS4J, this is fixed in http://ws.apache.org/wss4j/advisories/CVE-2015-0226.txt.asc, and this fix has been merged in to the WSS4J library used in WSO2 Carbon 4.2.0 products.