Skip to content

GHSA-h9ww-wjg4-jvvg CVE-2022-38512

Liferay Portal and Liferay DXP Fails to Check Permissions in Translation Module

Medium Maven
Severity
6.5 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.68%
Chance of exploitation in the next 30 days. Higher than 52.55% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-269 Improper Privilege Management
CWE-862 Missing Authorization
Fix
Available
2 packages have a fixed version

Description

The Translation module before v2.0.58 from Liferay Portal (v7.4.3.12 through v7.4.3.36), and Liferay DXP 7.4 update 8 through 36 does not check permissions before allowing a user to export a web content for translation, allowing attackers to download a web content page's XLIFF translation file via crafted URL.

Affected versions

Maven

PackageVulnerableFixed in
com.liferay.portal:release.dxp.bom
>= 7.4.13.u8, < 7.4.13.u37
7.4.13.u37
com.liferay:com.liferay.translation.web
< 2.0.58
2.0.58

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.4.13.u37

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

com.liferay:com.liferay.translation.web Maven → 2.0.58

maven
<dependency><groupId>com.liferay</groupId><artifactId>com.liferay.translation.web</artifactId><version>2.0.58</version></dependency>
gradle
implementation("com.liferay:com.liferay.translation.web:2.0.58")

Severity breakdown

CVSS 3.1 6.5

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

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

Weakness

CWE-269: Improper Privilege Management

The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.

How to prevent it
  • Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
  • Architecture and Design: Follow the principle of least privilege when assigning access rights to entities in a software system.
  • Architecture and Design: Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.

CWE-862: Missing Authorization

The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

How to prevent it
  • Architecture and Design: Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
  • Architecture and Design: Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor [REF-7].
  • Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
  • Architecture and Design: For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page. One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.
  • System Configuration, Installation: Use the access control capabilities of your operating system and server environment and define your access control lists accordingly. Use a "default deny" policy when defining these ACLs.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-66x6-8jgv-qpfh
Liferay Portal and Liferay DXP vulnerable to Stored Cross-site Scripting
Medium Also affects com.liferay.portal:release.dxp.bom
GHSA-rcc7-jx7p-hrv4
Liferay Portal and Liferay DXP vulnerable to store Cross-site Scripting
Medium Also affects com.liferay.portal:release.dxp.bom
GHSA-m5c7-5gv3-hcpf
Liferay Portal 7.4.0 and Liferay DXP have a reflected cross-site scripting (XSS) vulnerability
Medium Also affects com.liferay.portal:release.dxp.bom
GHSA-222w-xmc5-jhp3
Liferay Portal and Liferay DXP have a reflected cross-site scripting vulnerability
Medium Also affects com.liferay.portal:release.dxp.bom
GHSA-cg99-m88x-422c
Liferay Portal and Liferay DXP have a Denial Of Service via File Upload (DOS) vulnerability
Medium Also affects com.liferay.portal:release.dxp.bom
GHSA-c6g5-g6r7-q4j6
Liferay Portal and Liferay DXP vulnerable to Server-Side Request Forgery
Medium Also affects com.liferay.portal:release.dxp.bom
GHSA-6v93-frf9-2rp8
Liferay Portal and Liferay DXP vulnerable to Server-Side Request Forgery
High Also affects com.liferay.portal:release.dxp.bom
GHSA-qhp6-vp7c-g7xp
Liferay Cross-site Scripting vulnerability
Medium Also affects com.liferay.portal:release.dxp.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