# CVE-2024-25609: Liferay Portal and Liferay DXP's HtmlUtil.escapeRedirect Can Be Circumvented via Two Forward Slashes

> Attackers can bypass redirect protections to send users to malicious external URLs via crafted parameters in Liferay Portal.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 20 Feb 2024
- **Updated:** 23 Aug 2024
- **Also known as:** GHSA-3qq5-wcrx-4h8r

## What is CVE-2024-25609?

CVE-2024-25609 is a medium-severity vulnerability in Liferay Digital Experience Platform, published on 20 Feb 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

HtmlUtil.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.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2024-25609?

6 open source packages ship an affected version, including com.liferay.portal:release.dxp.bom and com.liferay.portal:release.portal.bom. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.liferay.portal:release.dxp.bom` | Maven | From 7.2.10.fp15 to 7.2.10.fp18 | None |
| `com.liferay.portal:release.dxp.bom` | Maven | From 7.2.10.fp15 to 7.2.10.fp18 | None |
| `com.liferay.portal:release.dxp.bom` | Maven | From 7.4.0 | 7.4.13.u9 |
| `com.liferay.portal:release.dxp.bom` | Maven | From 7.4.0 | 7.4.13.u9 |
| `com.liferay.portal:release.portal.bom` | Maven | From 7.2.0 | 7.4.3.13-ga13 |
| `com.liferay.portal:release.portal.bom` | Maven | From 7.2.0 | 7.4.3.13-ga13 |

Products: Liferay Digital Experience Platform, Liferay Liferay Portal.

## How do I fix CVE-2024-25609?

Upgrade com.liferay.portal:release.dxp.bom to 7.4.13.u9 or later.

## Is CVE-2024-25609 being exploited?

There is no known exploitation of CVE-2024-25609 in the wild and no public exploit code.

## Other vulnerabilities in Liferay Digital Experience Platform

- [CVE-2024-8980](https://insights.sbomify.com/CVE-2024-8980/): Liferay Portal and Liferay DXP Vulnerable to CSRF in the Script Console (critical 9.6)
- [CVE-2023-42496](https://insights.sbomify.com/CVE-2023-42496/): Liferay Portal and Liferay DXP vulnerable to reflected Cross-site Scripting (critical 9.6)
- [CVE-2023-42498](https://insights.sbomify.com/CVE-2023-42498/): Liferay Portal Language Override edit screen and Liferay DXP vulnerable to reflected Cross-site Scripting (critical 9.6)
- [CVE-2024-25147](https://insights.sbomify.com/CVE-2024-25147/): Liferay Portal and Liferay DXP vulnerable to Cross-site Scripting (critical 9.6)
- [CVE-2024-26269](https://insights.sbomify.com/CVE-2024-26269/): Liferay Portal Frontend JS module's portlet.js and Liferay DXP vulnerable to Cross-site Scripting (critical 9.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-25609 and fix it if it is affected.

What it is: CVE-2024-25609 is a medium-severity vulnerability in Liferay Digital Experience Platform, published on 20 Feb 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-25609 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.liferay.portal:release.dxp.bom (Maven): affected from 7.2.10.fp15 up to 7.2.10.fp18; no fix listed
- com.liferay.portal:release.dxp.bom (Maven): affected from 7.2.10.fp15 up to 7.2.10.fp18; no fix listed
- com.liferay.portal:release.dxp.bom (Maven): affected from 7.4.0; fixed in 7.4.13.u9
- com.liferay.portal:release.dxp.bom (Maven): affected from 7.4.0; fixed in 7.4.13.u9
- com.liferay.portal:release.portal.bom (Maven): affected from 7.2.0; fixed in 7.4.3.13-ga13
- com.liferay.portal:release.portal.bom (Maven): affected from 7.2.0; fixed in 7.4.3.13-ga13

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-25609/ (Markdown: https://insights.sbomify.com/CVE-2024-25609/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-25609
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-25609
- OSV: https://osv.dev/vulnerability/CVE-2024-25609

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-25609/
Summaries are generated and may contain mistakes; the official description above is the record.
