Published: 02nd December 2019
CVSS Score: 8.1 (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H)
WSO2 API Manager
WSO2 API Manager Analytics
WSO2 Enterprise Integrator
WSO2 IS as Key Manager
WSO2 Identity Server
WSO2 Identity Server Analytics
'TenantMgtService' allows an unauthorized user to register tenants.
If you are using the latest released version of the above mentioned affected products
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/.
|APIM||WSO2 API Manager||2.6.0||WSO2-CARBON-PATCH-4.4.0-5263|
WSO2 Enterprise Integrator
|IS KM||WSO2 IS as Key Manager||5.7.0||WSO2-CARBON-PATCH-4.4.0-5263|
|IS||WSO2 Identity Server||5.8.0|
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.
Applying the provided updates/patches to the affected versions of the products will enforce authorization to 'TenantMgtService' by default, and thereby fix this vulnerability. To authorize with the service, your applications will now have to send an HTTP Authorization header, in the same way calling other admin services of WSO2 products.
For other products
Upgrade the products to the latest released version which are not affected by this vulnerability.
In addition to the above-mentioned solution, we strongly recommend you to follow the below actions in order to ensure the security of your production environment:
- Check whether there are any suspicious tenants created. If so, take the necessary steps to deactivate them. You can check the tenants in the system and deactivate rogue ones by accessing the Management Console of the product (usually at https://:/carbon) and navigating to 'Home > Configure > Multitenancy > View Tenants'. If that check reveals rogue tenants in the system, then make sure to remove the folders created in the filesystem under those tenant names, inside WSO2 product distribution's location. Do that in all the WSO2 nodes of the deployment. That is to make sure any deployment artifact created by those tenants will be permanently removed. If the check does not reveal any suspicious tenants in the system, that means this vulnerability is not exploited in your deployment.
- Stop using 'TenantMgtService' for tenant registration and use 'TenantMgtAdminService' instead, since it is the most suitable for tenant management related functionality.
- Make sure WSO2's 'Security Guidelines for Production Deployment' are followed in order to harden your production deployment, if you have not done that already.
If you are using newer versions of affected products than the ones mentioned in the “SOLUTION” section, this vulnerability is fixed.