GHSA-43h9-p3j4-39hm CVE-2024-25607
Liferay Portal defaults to a low work factor for the default password hashing algorithm
High
Maven
- Severity
- 8.1 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 0.33%
- Chance of exploitation in the next 30 days. Higher than 25.79% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-916 Use of Password Hash With Insufficient Computational Effort
- Fix
- Available
- 3 packages have a fixed version
Description
The default password hashing algorithm (PBKDF2-HMAC-SHA1) in Liferay Portal 7.2.0 through 7.4.3.15, and older unsupported versions, and Liferay DXP 7.4 before update 16, 7.3 before update 4, 7.2 before fix pack 17, and older unsupported versions defaults to a low work factor, which allows attackers to quickly crack password hashes.
Affected versions
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| com.liferay.portal:com.liferay.portal.kernel | < 38.0.0 |
38.0.0 |
| com.liferay.portal:release.dxp.bom | >= 7.3.0, < 7.3.10.u4 |
7.3.10.u4 |
| com.liferay.portal:release.dxp.bom | < 7.2.10.fp17 |
7.2.10.fp17 |
| com.liferay.portal:release.dxp.bom | >= 7.4.0, < 7.4.13.u16 |
7.4.13.u16 |
| com.liferay.portal:release.portal.bom | < 7.4.3.14 |
7.4.3.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.portal:com.liferay.portal.kernel Maven → 38.0.0
- maven
<dependency><groupId>com.liferay.portal</groupId><artifactId>com.liferay.portal.kernel</artifactId><version>38.0.0</version></dependency>- gradle
implementation("com.liferay.portal:com.liferay.portal.kernel:38.0.0")
com.liferay.portal:release.dxp.bom Maven → 7.3.10.u4
- maven
<dependency><groupId>com.liferay.portal</groupId><artifactId>release.dxp.bom</artifactId><version>7.3.10.u4</version></dependency>- gradle
implementation("com.liferay.portal:release.dxp.bom:7.3.10.u4")
com.liferay.portal:release.portal.bom Maven → 7.4.3.14
- maven
<dependency><groupId>com.liferay.portal</groupId><artifactId>release.portal.bom</artifactId><version>7.4.3.14</version></dependency>- gradle
implementation("com.liferay.portal:release.portal.bom:7.4.3.14")
Severity breakdown
CVSS 3.1 8.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
Weakness
CWE-916: Use of Password Hash With Insufficient Computational Effort
The product generates a hash for a password, but it uses a scheme that does not provide a sufficient level of computational effort that would make password cracking attacks infeasible or expensive.
How to prevent it
- Architecture and Design: Use an adaptive hash function that can be configured to change the amount of computational effort needed to compute the hash, such as the number of iterations ("stretching") or the amount of memory required. Some hash functions perform salting automatically. These functions can significantly increase the overhead for a brute force attack compared to intentionally-fast functions such as MD5. For example, rainbow table attacks can become infeasible due to the high computing overhead. Finally, since computing power gets faster and cheaper over time, the technique can be reconfigured to increase the workload without forcing an entire replacement of the algorithm in use. Some hash functions that have one or more of these desired properties include bcrypt [REF-291], scrypt [REF-292], and PBKDF2 [REF-293]. While there is active debate about which of these is the most effective, they are all stronger than using salts with hash functions with very little computing overhead. Note that using these functions can have an impact on performance, so they require special consideration to avoid denial-of-service attacks. However, their configurability provides finer control over how much CPU and memory is used, so it could be adjusted to suit the environment's needs.
- Implementation, Architecture and Design: When using industry-approved techniques, use them correctly. Don't cut corners by skipping resource-intensive steps (CWE-325). These steps are often essential for preventing common attacks.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| CVE-2020-7961 Deserialization of Untrusted Data in Liferay Portal | Critical Known exploited | Also affects com.liferay.portal:com.liferay.portal.kernel |
| 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 |
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