Known Vulnerabilities

The following vulnerabilities are known to exist in Liferay Portal CE.  Users of older releases are strongly encouraged to upgrade to the latest Liferay Portal CE release.  Patches are only produced for the latest Liferay Portal CE release.  Source code modifications may be possible on older releases, but care must be taken to backport fixes that may not apply to older releases.

To obtain source or binary patches for each of the vulnerabilities, click on the name of the vulnerability, and look for links for source and binary patches.  To obtain a single cumulative source or binary patch for all known vulnerabilities, visit the Patch Details section of the Reporting page.  Note that the availability of the single cumulative binary patch may lag a day or two behind availability of the associated source patches.

Back

LPS-64441 Java Serialization Vulnerability

Date

Wed, 15 Jun 2016 10:01:00 +0000

Title

LPS-64441 Java Serialization Vulnerability

Description

A vulnerability known as "Java Deserialization Vulnerability" was discovered and Liferay Portal is potential vulnerable in the following locations:

  1. TunnelServlet:
  2. Spring-Remoting services

Severity

Severity 1

Workaround

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)

Issue Links

Note that some or all of these may not yet be accessible. The CST remains committed to full disclosure of all security issues once fully resolved.

Patching Instructions

See the Community Security Team Process page for details on working with source and binary patches.

Binary Patch Links

Note: The below links point to a download page which contains multiple binary patches with the following naming scheme: <Liferay-Version>-security-<patch-version>.zip. Be sure to use the latest patch for your Liferay release!

Note: Binary patches only apply to the release with which this issue is associated. Applying a binary patch to any other release will probably result in a broken install!

Source Patch Links

Note that source patches only apply to the release with which this issue is associated. Applying a source patch to any other release will probably result in a broken install! For Github URLs suffixed with .patch, removing this suffix will yield a graphical view of the patch

Notes

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.

  • Link 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.
  • Link 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.

Credit

Chris Dailey