Skip to content

Liferay Portal defaults to a low work factor for the default password hashing algorithm

High severity GitHub Reviewed Published Feb 20, 2024 to the GitHub Advisory Database • Updated Dec 11, 2024

Package

maven com.liferay.portal:com.liferay.portal.kernel (Maven)

Affected versions

< 38.0.0

Patched versions

38.0.0
maven com.liferay.portal:release.dxp.bom (Maven)
>= 7.3.0, < 7.3.10.u4
< 7.2.10.fp17
>= 7.4.0, < 7.4.13.u16
7.3.10.u4
7.2.10.fp17
7.4.13.u16
maven com.liferay.portal:release.portal.bom (Maven)
< 7.4.3.14
7.4.3.14

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.

References

Published by the National Vulnerability Database Feb 20, 2024
Published to the GitHub Advisory Database Feb 20, 2024
Reviewed Dec 11, 2024
Last updated Dec 11, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

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

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

EPSS score

0.087%
(39th percentile)

Weaknesses

CVE ID

CVE-2024-25607

GHSA ID

GHSA-43h9-p3j4-39hm

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.