CVE-2024-25609
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 · uneditedHtmlUtil.escapeRedirect in Liferay Portal 7.2.0 through 7.4.3.12, and older unsupported versions, and Liferay DXP 7.4 before update 9, 7.3 service pack 3, 7.2 fix pack 15 through 18, and older unsupported versions can be circumvented by using two forward slashes, which allows remote attackers to redirect users to arbitrary external URLs via the (1) 'redirect` parameter (2) `FORWARD_URL` parameter, and (3) others parameters that rely on HtmlUtil.escapeRedirect. This vulnerability is the result of an incomplete fix in CVE-2022-28977.
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 · moderate confidenceThe HtmlUtil.escapeRedirect function in Lifer Portal 7.2.0-7.4.3.12 and DXP 7.4 before update 9, 7.3 SP3, and 7.2 FP15-18 can be bypassed using double forward slashes (//), allowing attackers to redirect users to arbitrary external URLs via the redirect parameter, FORWARD_URL parameter, and other parameters relying on this utility. This is an incomplete fix of CVE-2022-28977.
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< 7.2= 7.2= 7.3= 7.4< 7.4.3.13CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Lifer Portal or DXP versionCheck the portal's build information or deployment metadata. Typically found in portal-impl.jar or via the Lifer Control Panel under Server Information. Look for a version string like 7.2.x, 7.3.x, or 7.4.x.Affected if The installed version is Lifer Portal < 7.4.3.13, or DXP 7.2 (any FP before 19), 7.3 (any SP before 3), or 7.4 (any update before 9).
-
Determine if redirect or FORWARD_URL parameters are accessibleReview web application configuration and exposed endpoints. Check for URL parameters named 'redirect', 'FORWARD_URL', or similar parameters that accept URL values and are processed by the HtmlUtil.escapeRedirect function.Affected if These parameters are exposed in public-facing URLs without additional validation layers.
-
Test for double-slash bypass in redirect handlingSubmit a test request to an affected endpoint using a parameter value like '//example.com' (double slash followed by an external domain). Compare the behavior against a properly sanitized redirect such as '/internal/page'.Affected if The application allows redirects to '//example.com' which resolves to an external domain, indicating the bypass is present.
-
Inspect HtmlUtil.escapeRedirect implementationLocate the HtmlUtil class in the portal source or decompiled JAR. Examine the escapeRedirect method to verify whether it handles or strips double forward slashes at the beginning of redirect URLs.Affected if The escapeRedirect method lacks logic to block or normalize URLs starting with '//' before constructing the final redirect destination.
You are affected if your Lifer installation version falls within the vulnerable ranges AND your application exposes redirect-handling parameters that use the HtmlUtil.escapeRedirect function without additional external URL validation.
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.27.4.3.13
Upgrade to Lifer Portal 7.4.3.13+, DXP 7.4 update 9+, 7.3 SP3+, or 7.2 FP19+ to obtain the complete fix that properly handles the double-slash bypass.
Lifera Portal 7.4.3.13+ or Liferix DXP 7.4 Update 9+ / DXP 7.3 Service Pack 4+ / DXP 7.2 Fix Pack 19+
- 1. Identify the current Livery DXP/Portal version by checking the Liferix Control Panel or portal-ext.properties
- 2. For Liferay Portal 7.4.x: Upgrade to version 7.4.3.13 or later
- 3. For Liferix DXP 7.4: Apply Update 9 or later
- 4. For Liferix DXP 7.3: Apply Service Pack 4 or later
- 5. For Liferix DXP 7.2: Apply Fix Pack 19 or later
- 6. After upgrade, verify the HtmlUtil.escapeRedirect function properly rejects URLs starting with double slashes (//)
- 7. Test that legitimate redirect parameters work correctly after the patch
- 8. Review application logs for any redirect-related errors post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2024-25609 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-25609 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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