GHSA-87x7-pwrx-jch7 CVE-2021-29040
Liferay Portal and Liferay DXP Reveals Data via Overly Verbose Error Messages
Medium
Maven
- Severity
- 5.3 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 1.08%
- Chance of exploitation in the next 30 days. Higher than 65.14% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-209 Generation of Error Message Containing Sensitive Information
- Fix
- Available
- 2 packages have a fixed version
Description
The JSON web services in Liferay Portal 7.3.4 and earlier, and Liferay DXP 7.0 before fix pack 97, 7.1 before fix pack 20 and 7.2 before fix pack 10 may provide overly verbose error messages, which allows remote attackers to use the contents of error messages to help launch another, more focused attacks via crafted inputs.
Affected versions
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| com.liferay.portal:release.dxp.bom | < 7.0.10.fp97 |
7.0.10.fp97 |
| com.liferay.portal:release.dxp.bom | >= 7.1.0, < 7.1.10.fp20 |
7.1.10.fp20 |
| com.liferay.portal:release.dxp.bom | >= 7.2.0, < 7.2.10.fp10 |
7.2.10.fp10 |
| com.liferay.portal:release.portal.bom | < 7.3.5 |
7.3.5 |
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.fp97
- maven
<dependency><groupId>com.liferay.portal</groupId><artifactId>release.dxp.bom</artifactId><version>7.0.10.fp97</version></dependency>- gradle
implementation("com.liferay.portal:release.dxp.bom:7.0.10.fp97")
com.liferay.portal:release.portal.bom Maven → 7.3.5
- maven
<dependency><groupId>com.liferay.portal</groupId><artifactId>release.portal.bom</artifactId><version>7.3.5</version></dependency>- gradle
implementation("com.liferay.portal:release.portal.bom:7.3.5")
Severity breakdown
CVSS 3.1 5.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Weakness
CWE-209: Generation of Error Message Containing Sensitive Information
The product generates an error message that includes sensitive information about its environment, users, or associated data.
How to prevent it
- Implementation: Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success. If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files. Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.
- Implementation: Handle exceptions internally and do not display errors containing potentially sensitive information to a user.
- Implementation: Use naming conventions and strong types to make it easier to spot when sensitive data is being used. When creating structures, objects, or other complex entities, separate the sensitive and non-sensitive data as much as possible.
- Implementation, Build and Compilation: Debugging information should not make its way into a production release.
- Implementation, Build and Compilation: Debugging information should not make its way into a production release.
- System Configuration: Where available, configure the environment to use less verbose error messages. For example, in PHP, disable the display_errors setting during configuration, or at runtime using the error_reporting() function.
- System Configuration: Create default error pages or messages that do not leak any information.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why 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 |
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