©2019 WSO2
This website uses cookies so that we can provide you with the best user experience. Read our Cookie Policy to find out more.
If you wish to disable cookies you can do so from your browser.
I Understand
| Security Patch | Product Version | Description |
|---|---|---|
| WSO2-CARBON-PATCH-4.4.0-1665 | 3.5.1 | Release 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-0831 | 3.5.1 | Release 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-1152 | 3.5.1 | Release 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-1105 | 3.5.1 | Release 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-1184 | 3.5.1 | Release Date - Sep 4, 2017 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 has not been properly encoded to prevent XSS. Security Advisory Link |
| WSO2-CARBON-PATCH-4.4.0-1195 | 3.5.1 | Release Date - Sep 4, 2017 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 has not been properly encoded to prevent XSS. Security Advisory Link |
| WSO2-CARBON-PATCH-4.4.0-1316 | 3.5.1 | Release 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-1418 | 3.5.1 | Release 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-0911 | 3.5.1 | Release 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-1021 | 3.5.1 | Release 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 |
| WSO2-CARBON-PATCH-4.4.0-0867 | 3.5.1 | Release 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-0660 | 3.5.1 | Release Date - Jan 31, 2017 Potential XSS vulnerability in Carbon Governance, Carbon Registry, Tenant management, Carbon Webapp Management components. Security Advisory Link |
| WSO2-CARBON-PATCH-4.4.0-0665 | 3.5.1 | Release Date - Jan 31, 2017 Potential XSS vulnerability in Carbon Governance, Carbon Registry, Tenant management, Carbon Webapp Management components. Security Advisory Link |
| WSO2-CARBON-PATCH-4.4.0-0581 | 3.5.1 | Release Date - Jan 31, 2017 Potential Arbitrary File Read(AFR) and Arbitrary Directory Read (ADR) vulnerabilities in carbon-commons component Security Advisory Link |
| WSO2-CARBON-PATCH-4.4.0-0586 | 3.5.1 | Release Date - Jan 31, 2017 Potential XSS vulnerability in carbon WSDL tool Security Advisory Link |
| WSO2-CARBON-PATCH-4.4.0-0618 | 3.5.1 | Release Date - Jan 31, 2017 Potential XML External Entity (XXE) vulnerability WSDL tool of WSO2 Carbon Commons component Security Advisory Link |
| WSO2-CARBON-PATCH-4.4.0-0628 | 3.5.1 | Release Date - Jan 31, 2017 Potential XML External Entity (XXE) vulnerability in Carbon Try-it tool of WSO2 Carbon Commons component Security Advisory Link |
| WSO2-CARBON-PATCH-4.4.0-0769 | 3.5.1 | Release Date - Jan 31, 2017 Potential Stored XSS vulnerability in WSO2 Server Roles Management UI component Security Advisory Link |
| WSO2-CARBON-PATCH-4.4.0-0718 | 3.5.1 | Release Date - Jan 31, 2017 Potential XSS vulnerability in WSO2 Carbon UI and Message Flows UI components Security Advisory Link |
| WSO2-CARBON-PATCH-4.4.0-0720 | 3.5.1 | Release Date - Jan 31, 2017 Potential XSS vulnerability in WSO2 Carbon UI and Message Flows UI components Security Advisory Link |
| WSO2-CARBON-PATCH-4.4.0-0630 | 3.5.1 | Release Date - Jan 31, 2017 Potential XSS vulnerability in WSO2 Carbon New Data Sources UI component Security Advisory Link |
| Update via WSO2 Update Manager | 3.5.1 | Release 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 |
| WSO2-CARBON-PATCH-4.4.0-0538 | 3.5.1 | Release Date - Nov 8, 2016 When a user browses a pages 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 Manager | 3.5.1 | Release 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 |
| WSO2-CARBON-PATCH-4.4.0-0385 | 3.5.0 | Release 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-0353 | 3.5.0 | Release 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-0203 | 3.5.0 | Release Date - Aug 12, 2016 Preventing a possible server shutdown through a Cross Site Request Forgery (CSRF) attack. Security Advisory Link |
| WSO2-CARBON-PATCH-4.4.0-0241 | 3.5.0 | Release Date - Aug 12, 2016 Upgrade to Tomcat 7.0.69 to support Tomcat level security fixes and Security Headers in HTTP Response Security Advisory Link |
| WSO2-CARBON-PATCH-4.4.0-0236 | 3.5.0 | Release Date - Aug 12, 2016 Upgrade to Tomcat 7.0.69 to support Tomcat level security fixes and Security Headers in HTTP Response Security Advisory Link |
| WSO2-CARBON-PATCH-4.4.0-0213 | 3.5.0 | Release Date - Aug 12, 2016 Preventing a possible server shutdown through a Cross Site Request Forgery (CSRF) attack. Security Advisory Link |
| WSO2-CARBON-PATCH-4.2.0-1826 | 3.1.0 | Release 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-1825 | 3.2.2 / 3.2.1 / 3.2.0 / 3.1.1 | Release 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-0176 | 3.5.0 | Release 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-1699 | 3.2.2 / 3.2.1 / 3.2.0 / 3.1.0 / 3.1.1 | Release 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-0667 | 3.0.0 | Release 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.4.0-0042 | 3.5.0 | Release 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-1261 | 3.2.2 / 3.2.1 / 3.2.0 / 3.1.1 / 3.1.0 | Release 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.4.0-0016 | 3.5.0 | Release 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-1636 | 3.2.2/ 3.2.1 / 3.2.0 / 3.1.0 / 3.1.1 | Release 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-1464 | 3.2.2/ 3.2.1 / 3.2.0 / 3.1.0 / 3.1.1 | Release 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-1095 | 3.2.2 / 3.2.1 / 3.2.0 / 3.1.1 / 3.1.0 | Release 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. |