Skip to content

GHSA-v377-8f8f-532h CVE-2020-13445

Liferay Portal and Liferay DXP Vulnerable to Arbitrary Code Execution

High Maven
Severity
8.8 / 10
High · CVSS 3.1
Exploit chance (EPSS)
3.69%
Chance of exploitation in the next 30 days. Higher than 89.69% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Fix
Available
2 packages have a fixed version

Description

In Liferay Portal before 7.3.2 and Liferay DXP 7.0 before fix pack 92, 7.1 before fix pack 18, and 7.2 before fix pack 6, the template API does not restrict user access to sensitive objects, which allows remote authenticated users to execute arbitrary code via crafted FreeMarker and Velocity templates.

Affected versions

Maven

PackageVulnerableFixed in
com.liferay.portal:release.dxp.bom
>= 7.0.0, < 7.0.10.fp92
7.0.10.fp92
com.liferay.portal:release.dxp.bom
>= 7.1.0, < 7.1.10.fp18
7.1.10.fp18
com.liferay.portal:release.dxp.bom
>= 7.2.0, < 7.2.10.fp6
7.2.10.fp6
com.liferay.portal:release.portal.bom
< 7.3.2
7.3.2

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

com.liferay.portal:release.dxp.bom Maven → 7.0.10.fp92

maven
<dependency><groupId>com.liferay.portal</groupId><artifactId>release.dxp.bom</artifactId><version>7.0.10.fp92</version></dependency>
gradle
implementation("com.liferay.portal:release.dxp.bom:7.0.10.fp92")

com.liferay.portal:release.portal.bom Maven → 7.3.2

maven
<dependency><groupId>com.liferay.portal</groupId><artifactId>release.portal.bom</artifactId><version>7.3.2</version></dependency>
gradle
implementation("com.liferay.portal:release.portal.bom:7.3.2")

Severity breakdown

CVSS 3.1 8.8

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Weakness

CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.

How to prevent it
  • Requirements: Programming languages and supporting technologies might be chosen which are not subject to these issues.
  • Implementation: Utilize an appropriate mix of allowlist and denylist parsing to filter control-plane syntax from all input.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-2j97-4jmq-c4xf
Liferay Portal Vulnerable to Reflected XSS via the selectedLanguageId Parameter
Medium Also affects com.liferay.portal:release.portal.bom
GHSA-56jv-4ww3-65mw
Liferay Portal is vulnerable to XSS in the Blogs widget
Medium Also affects com.liferay.portal:release.portal.bom
GHSA-f5vh-4rj2-w8r8
Liferay Portal is vulnerable to DNS rebinding attacks
Medium Also affects com.liferay.portal:release.portal.bom
GHSA-8hw3-ghwv-crfh
Liferay Portal vulnerable to password enumeration
Medium Also affects com.liferay.portal:release.portal.bom
GHSA-gv7w-jh8g-vr73
Liferay Portal Does Not Limit Access to APIs Before Email Verification
Medium Also affects com.liferay.portal:release.portal.bom
GHSA-gh4w-8qgq-8w9r
Liferay Portal Vulnerable to CSRF in Headless APIs
Medium Also affects com.liferay.portal:release.portal.bom
GHSA-xcj6-xpjg-c4xr
Liferay Portal Stores Password Reset Tokens in Plain Text
Medium Also affects com.liferay.portal:release.portal.bom
GHSA-vgqx-447m-wvcj
Liferay Portal Vulnerable to DoS via Crafted Headless API Request
High Also affects com.liferay.portal:release.portal.bom
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor