# CVE-2024-25143: Liferay Portal denial of service (memory consumption)

> Authenticated attackers can cause denial of service via memory exhaustion by uploading crafted PNG images to the Document and Media widget.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Feb 2024
- **Updated:** 2 Oct 2024
- **Also known as:** GHSA-87m3-6qj3-p3xh

## What is CVE-2024-25143?

CVE-2024-25143 is a medium-severity denial of service vulnerability in Liferay Digital Experience Platform, published on 7 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Document and Media widget In Liferay Portal 7.2.0 through 7.3.6, and older unsupported versions, and Liferay DXP 7.3 before service pack 3, 7.2 before fix pack 13, and older unsupported versions, does not limit resource consumption when generating a preview image, which allows remote authenticated users to cause a denial of service (memory consumption) via crafted PNG images.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.liferay.portal:release.portal.bom` | Maven | From 7.2.0 | 7.3.7 |
| `com.liferay.portal:release.portal.bom` | Maven | From 7.2.0 | 7.3.7 |

Products: Liferay Digital Experience Platform, Liferay Liferay Portal.

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

Upgrade com.liferay.portal:release.portal.bom to 7.3.7 or later.

## Is CVE-2024-25143 being exploited?

There is no known exploitation of CVE-2024-25143 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-25143 and fix it if it is affected.

What it is: CVE-2024-25143 is a medium-severity denial of service vulnerability in Liferay Digital Experience Platform, published on 7 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-25143 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.liferay.portal:release.portal.bom (Maven): affected from 7.2.0; fixed in 7.3.7
- com.liferay.portal:release.portal.bom (Maven): affected from 7.2.0; fixed in 7.3.7

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-25143/ (Markdown: https://insights.sbomify.com/CVE-2024-25143/index.md)
```

## Sources

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

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