GHSA-vjj4-qwcm-552h BIT-liferay-2022-42124 CVE-2022-42124
Inefficient Regular Expression Complexity in Liferay Portal
- Severity
- 7.5 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 1.35%
- Chance of exploitation in the next 30 days. Higher than 71.53% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-1333 Inefficient Regular Expression Complexity
- Fix
7.4.3.5- Upgrade com.liferay.portal:release.portal.bom to this version or later
Description
ReDoS vulnerability in LayoutPageTemplateEntryUpgradeProcess in Liferay Portal 7.3.2 through 7.4.3.4 and Liferay DXP 7.2 fix pack 9 through fix pack 18, 7.3 before update 4, and DXP 7.4 GA allows remote attackers to consume an excessive amount of server resources via a crafted payload injected into the 'name' field of a layout prototype.
Affected versions
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| com.liferay.portal:release.portal.bom | >= 7.3.2, < 7.4.3.5 |
7.4.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.portal.bom Maven → 7.4.3.5
- maven
<dependency><groupId>com.liferay.portal</groupId><artifactId>release.portal.bom</artifactId><version>7.4.3.5</version></dependency>- gradle
implementation("com.liferay.portal:release.portal.bom:7.4.3.5")
Severity breakdown
CVSS 3.1 7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Weakness
CWE-1333: Inefficient Regular Expression Complexity
The product uses a regular expression with a worst-case computational complexity that is inefficient and possibly exponential.
How to prevent it
- Architecture and Design: Use regular expressions that do not support backtracking, e.g. by removing nested quantifiers.
- System Configuration: Set backtracking limits in the configuration of the regular expression implementation, such as PHP's pcre.backtrack_limit. Also consider limits on execution time for the process.
- Implementation: Do not use regular expressions with untrusted input. If regular expressions must be used, avoid using backtracking in the expression.
- Implementation: Limit the length of the input that the regular expression will process.
References
Advisories
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