CVE-2024-25608
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.18, and older unsupported versions, and Liferay DXP 7.4 before update 19, 7.3 before update 4, 7.2 before fix pack 19, and older unsupported versions can be circumvented by using the 'REPLACEMENT CHARACTER' (U+FFFD), which allows remote attackers to redirect users to arbitrary external URLs via the (1) 'redirect` parameter (2) `FORWARD_URL` parameter, (3) `noSuchEntryRedirect` parameter, and (4) others parameters that rely on HtmlUtil.escapeRedirect.
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 confidenceLifer Portal/DXP's HtmlUtil.escapeRedirect function, intended to prevent open redirect attacks by validating redirect URLs are internal, can be bypassed by embedding the Unicode REPLACEMENT CHARACTER (U+FFFD) in the URL. This allows attackers to redirect users to malicious external sites via the redirect, FORWARD_URL, noSuchEntryRedirect, and similar parameters.
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.19CVSS 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/DXP installation versionLocate the version file or portal properties (typically in portal-impl.jar or via the Control Panel > Configuration > Server Administration > Portal Properties). Alternatively, check the marketplace or deploy folder for the portal WAR version.Affected if The installed version matches Lifer DXP 7.2, 7.3, 7.4, or Lifer Portal versions prior to 7.4.3.19 (including any version < 7.2).
-
Confirm redirect parameter exposureIdentify whether the application exposes redirect handling parameters such as 'redirect', 'FORWARD_URL', 'noSuchEntryRedirect', or similar URL redirection parameters in HTTP requests.Affected if The application accepts and processes redirect parameters in URL query strings or form submissions.
-
Inspect URL handling for Unicode U+FFFDReview application logs, access logs, or WAF/proxy logs for any requests containing the Unicode REPLACEMENT CHARACTER (U+FFFD, hex EF BF BD) in redirect-related parameters.Affected if Requests containing U+FFFD embedded in redirect URLs have been processed by the application without rejection.
-
Check HtmlUtil.escapeRedirect implementationIf code access is available, locate the HtmlUtil class and inspect the escapeRedirect method for validation logic and whether it explicitly blocks or strips the U+FFFD character.Affected if The escapeRedirect method does not filter or reject URLs containing the U+FFFD Unicode character, allowing external redirects.
A user is affected if their Lifer Portal/DXP version falls within the vulnerable range (7.2, 7.3, 7.4, or Portal < 7.4.3.19) and the application processes redirect parameters that could contain the U+FFFD Unicode character to bypass internal 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.19
Apply the vendor-supplied patches/updates: Lifer Portal 7.4.3.19+, DXP 7.4 update 19+, DXP 7.3 update 4+, DXP 7.2 fix pack 19+. If patching is not immediately feasible, implement WAF rules to block URLs containing U+FFFD and audit all redirect parameter usage.
Liferay Portal 7.4.3.19+; Liferay DXP 7.4 Update 19+; Liferay DXP 7.3 Update 4+; Liferary DXP 7.2 Fix Pack 19+
- Upgrade Liferay Portal 7.4.x to version 7.4.3.19 or later
- If using Liferay DXP 7.4, apply Update 19 or later
- If using Lervlet DXP 7.3, apply Update 4 or later
- If using Liferay DXP 7.2, apply Fix Pack 19 or later
- After upgrade, verify that redirect parameters are properly validated and no longer accept U+FFFD character to bypass the redirect protection
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-25608 — 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-25608 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