Skip to content

GHSA-4585-28v2-8h46 CVE-2024-25150

Liferay Portal and Liferay DXP Information Disclosure Vulnerability in the Control Panel

Medium Maven
Severity
4.3 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.44%
Chance of exploitation in the next 30 days. Higher than 38.17% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-201 Insertion of Sensitive Information Into Sent Data
Fix
Available
2 packages have a fixed version

Description

Information disclosure vulnerability in the Control Panel in Liferay Portal 7.2.0 through 7.4.2, and older unsupported versions, and Liferay DXP 7.3 before update 4, 7.2 before fix pack 19, and older unsupported versions allows remote authenticated users to obtain a user's full name from the page's title by enumerating user screen names.

Affected versions

Maven

PackageVulnerableFixed in
com.liferay.portal:release.dxp.bom
< 7.2.10.fp19
7.2.10.fp19
com.liferay.portal:release.dxp.bom
>= 7.3.0, < 7.3.10.u4
7.3.10.u4
com.liferay.portal:release.portal.bom
>= 7.2.0, < 7.4.3.4-ga4
7.4.3.4-ga4

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.2.10.fp19

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

com.liferay.portal:release.portal.bom Maven → 7.4.3.4-ga4

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

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-201: Insertion of Sensitive Information Into Sent Data

The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.

How to prevent it
  • Requirements: Specify which data in the software should be regarded as sensitive. Consider which types of users should have access to which types of data.
  • Implementation: Ensure that any possibly sensitive data specified in the requirements is verified with designers to ensure that it is either a calculated risk or mitigated elsewhere. Any information that is not necessary to the functionality should be removed in order to lower both the overhead and the possibility of security sensitive data being sent.
  • System Configuration: Setup default error messages so that unexpected errors do not disclose sensitive information.
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

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