# CVE-2020-15839: Unrestricted Upload of File with Dangerous Type in Liferay Portal and Liferay DXP > Authenticated users can cause denial of service by uploading excessively large files due to missing size restrictions in Liferay Portal. - **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:** 22 Sep 2020 - **Updated:** 4 Aug 2024 - **Also known as:** BIT-liferay-2020-15839, GHSA-c7f6-4vx5-4263 ## What is CVE-2020-15839? CVE-2020-15839 is a medium-severity denial of service vulnerability in Liferay Digital Experience Platform, published on 22 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Liferay Portal before 7.3.3, and Liferay DXP 7.1 before fix pack 18 and 7.2 before fix pack 6, does not restrict the size of a multipart/form-data POST action, which allows remote authenticated users to conduct denial-of-service attacks by uploading large files. Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type) ## Which versions are affected by CVE-2020-15839? 5 open source packages ship an affected version, including com.liferay.portal:release.dxp.bom and liferay. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `com.liferay.portal:release.dxp.bom` | Maven | All versions | 7.1.10.fp18 | | `com.liferay.portal:release.dxp.bom` | Maven | All versions | 7.1.10.fp18 | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.2.1 | 7.2.10.fp6 | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.2.1 | 7.2.10.fp6 | | `liferay` | Bitnami | From 7.1.0 to 7.1.0 | None | Products: Liferay Digital Experience Platform, Liferay Liferay Portal. ## How do I fix CVE-2020-15839? Upgrade com.liferay.portal:release.dxp.bom to a fixed version for your release line: 7.1.10.fp18 or 7.2.10.fp6. ## Is CVE-2020-15839 being exploited? There is no known exploitation of CVE-2020-15839 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-2020-15839 and fix it if it is affected. What it is: CVE-2020-15839 is a medium-severity denial of service vulnerability in Liferay Digital Experience Platform, published on 22 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2020-15839 in the wild and no public exploit code. Affected packages and fixed versions: - com.liferay.portal:release.dxp.bom (Maven): affected all versions; fixed in 7.1.10.fp18 - com.liferay.portal:release.dxp.bom (Maven): affected all versions; fixed in 7.1.10.fp18 - com.liferay.portal:release.dxp.bom (Maven): affected from 7.2.1; fixed in 7.2.10.fp6 - com.liferay.portal:release.dxp.bom (Maven): affected from 7.2.1; fixed in 7.2.10.fp6 - liferay (Bitnami): affected from 7.1.0 up to 7.1.0; no fix listed 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-2020-15839/ (Markdown: https://insights.sbomify.com/CVE-2020-15839/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-15839 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-15839 - OSV: https://osv.dev/vulnerability/CVE-2020-15839 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-15839/ Summaries are generated and may contain mistakes; the official description above is the record.