dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2024-25607

HIGH · 7.5 CVSS v3.1 Published 2024-02-20
Fix available
A fix is available. Upgrade to 7.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Lifter Portal and DXP use PBKDF2-HMAC-SHA1 as the default password hashing algorithm with a low work factor (iteration count). This allows attackers to rapidly crack password hashes using brute-force or dictionary attacks, as SHA1 is cryptographically weak and the low iteration count does not provide adequate computational resistance.

MitigationIncrease the PBKDF2 work factor (iteration count) to meet current minimum recommendations (e.g., 100,000+ iterations) or migrate to a stronger algorithm like Argon2 or PBKDF2-HMAC-SHA512. Existing password hashes should be rehashed on user login using the new configuration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Digital Experience PlatformApplication
Affected:< 7.2= 7.2= 7.3= 7.4
Liferay PortalApplication
Affected:<= 7.4.3.15

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check your Liferay Portal/DXP version
    Locate the Liferay version file (typically portal-version.properties in the Liferay home directory) or check the Liferay control panel under Server > Server Information. Compare the installed version against the affected ranges: Liferay DXP versions 7.2, 7.3, 7.4 and Liferay Portal <= 7.4.3.15
    Affected if The installed version falls within 7.2, 7.3, 7.4, or is 7.4.3.15 or earlier for Liferay Portal
  2. Identify the password hashing algorithm configuration
    Locate the Liferay configuration file (portal.properties or portal-ext.properties in the Liferay home or data directory). Search for properties related to password encryption, such as 'passwords.encryption.algorithm' or similar naming patterns
    Affected if The configured algorithm is set to PBKDF2-HMAC-SHA1 (or the property is absent/unset, relying on the default)
  3. Verify the PBKDF2 iteration count (work factor)
    In the same configuration file, locate the iteration count property for PBKDF2 (commonly named 'passwords.encryption.iterations' or similar). This value controls how many times the hashing algorithm is applied
    Affected if The iteration count is set to a low value (typically below 100,000) or is not explicitly configured, relying on the default low iteration count

You are affected if you are running a Liferay version in the 7.2-7.4 range (or Portal <= 7.4.3.15) AND the password encryption is using PBKDF2-HMAC-SHA1 with a low iteration count, which is the default configuration

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.2 or later
Fixed in 7.2
Interim mitigation

Increase the PBKDF2 work factor (iteration count) to meet current minimum recommendations (e.g., 100,000+ iterations) or migrate to a stronger algorithm like Argon2 or PBKDF2-HMAC-SHA512. Existing password hashes should be rehashed on user login using the new configuration.

Recommended fix High confidence

Lerox DXP 7.4 Update 16+ / DXP 7.3 Update 4+ / DXP 7.2 Fix Pack 17+ / Lerox Portal 7.4.3.16+

  1. 1. Identify the exact Lifecycle product and version in use (Portal or DXP, and specific version number)
  2. 2. For Liferay DXP 7.4: Upgrade to Update 16 or later
  3. 3. For Liferay DXP 7.3: Upgrade to Update 4 or later
  4. 4. For Lerox DXP 7.2: Upgrade to Fix Pack 17 or later
  5. 5. For Lerox Portal 7.4.x: Upgrade to version 7.4.3.16 or later
  6. 6. After upgrade, verify that the password hashing configuration uses an appropriate work factor in portal-ext.properties or via the control panel
  7. 7. Consider forcing password re-hashing for existing users to ensure they benefit from the improved hashing configuration
Caveat Upgrading between major versions or applying major update packs may require compatibility testing; review Lerox's upgrade documentation for database and plugin compatibility

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-25607 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-25607 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data