Skip to content

GHSA-xph3-vjcq-g488 BIT-liferay-2023-3426 CVE-2023-3426

Liferay Portal and Liferay DXP Organization Selector Does Not Check User Permissions

Medium Maven
Severity
4.3 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.58%
Chance of exploitation in the next 30 days. Higher than 47.54% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-425 Direct Request ('Forced Browsing')
CWE-862 Missing Authorization
Fix
4.0.14
Upgrade com.liferay:com.liferay.organizations.item.selector.web to this version or later

Description

The organization selector before 4.0.14 from Liferay Portal (7.4.3.81 through 7.4.3.85), and Liferay DXP 7.4 update 81 through 85 does not check user permission, which allows remote authenticated users to obtain a list of all organizations.

Affected versions

Maven

PackageVulnerableFixed in
com.liferay.portal:release.dxp.bom
>= 7.4.143.u81, <= 7.4.143.u85
No fix yet
com.liferay:com.liferay.organizations.item.selector.web
< 4.0.14
4.0.14

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:com.liferay.organizations.item.selector.web Maven → 4.0.14

maven
<dependency><groupId>com.liferay</groupId><artifactId>com.liferay.organizations.item.selector.web</artifactId><version>4.0.14</version></dependency>
gradle
implementation("com.liferay:com.liferay.organizations.item.selector.web:4.0.14")

Severity breakdown

CVSS 3.1 4.3

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

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

Weakness

CWE-425: Direct Request ('Forced Browsing')

The web application does not adequately enforce appropriate authorization on all restricted URLs, scripts, or files.

How to prevent it
  • Architecture and Design, Operation: Apply appropriate access control authorizations for each access to all restricted URLs, scripts or files.
  • Architecture and Design: Consider using MVC based frameworks such as Struts.

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