Description
A vulnerability known as "Java Deserialization Vulnerability" was discovered and Liferay Portal is potential vulnerable in the following locations:
- TunnelServlet:
- Spring-Remoting services
By default, these services are secured to only accept requests from the loopback (127.0.0.1) and server’s default host interface (e.g. eth0).
- For those not using remote staging or any other remote services via Liferay's tunnel-web: tunnel.servlet.hosts.allowed=127.0.0.1, SERVER_IP
This is the default value in portal.properties. Thus, unless you have customized the property, there is nothing to adjust. - For those using remote-staging or other remote services via the tunnel-web, you may configure tunnel.servlet.hosts.allowed to list the IP address for all clients of the tunnel-web services (e.g. your staging server, etc)
Severity
Severity 1
Fixed Version(s)
Note that there are two binary patches which fix this issue, as well as all previous CST fixes for this release. You only need to apply one of these, not both.
- Binary Patch 1: The "complete" patch is a patch which merges the fixes for all reports into the original Liferay JAR files, which you can use to overwrite the existing .JAR files in your Liferay deployment. See the README file on SourceForge for more details. This patch is used in cases where classloading issues prevent proper deployment of EXT plugins, such as GlassFish.
- Binary Patch 2: The "diff" patch - this is an ordinary binary EXT-based patch (using
ext-XXXXX.jar) like those previously issued by the CST and can be applied to most deployments. If you've successfully applied CST patches in the past, then this is the patch for you. - Source Patch: Details for working with source patches can be found on the Patching Liferay Portal page.
Acknowledgments
This issue was reported by Chris Dailey
Publication date: Wed, 15 Jun 2016 10:01:00 +0000