# CVE-2020-15842: Liferay Portal and Liferay DXP have Insecure Deserialization Vulnerability > Man-in-the-middle attackers can execute arbitrary code via crafted serialized payloads due to insecure deserialization in Liferay Portal. - **Severity:** High 8.1 (`CVSS:3.1/AC:H/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 20 Jul 2020 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-mg3r-9jh8-33r9 ## What is CVE-2020-15842? CVE-2020-15842 is a high-severity unsafe deserialization vulnerability in Liferay Digital Experience Platform, published on 20 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Liferay Portal before 7.3.0, and Liferay DXP 7.0 before fix pack 90, 7.1 before fix pack 17, and 7.2 before fix pack 5, allows man-in-the-middle attackers to execute arbitrary code via crafted serialized payloads, because of insecure deserialization. Weakness: CWE-502 (Deserialization of Untrusted Data) ## Which versions are affected by CVE-2020-15842? 8 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.0.0 | 7.0.10.fp90 | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.0.0 | 7.0.10.fp90 | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.1.0 | 7.1.10.fp17 | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.1.0 | 7.1.10.fp17 | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.2.0 | 7.2.10.fp5 | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.2.0 | 7.2.10.fp5 | | `com.liferay.portal:release.portal.bom` | Maven | All versions | 7.3.0 | | `com.liferay.portal:release.portal.bom` | Maven | All versions | 7.3.0 | Products: Liferay Digital Experience Platform, Liferay Liferay Portal. ## How do I fix CVE-2020-15842? Upgrade com.liferay.portal:release.dxp.bom to a fixed version for your release line: 7.0.10.fp90, 7.1.10.fp17 or 7.2.10.fp5. ## Is CVE-2020-15842 being exploited? There is no known exploitation of CVE-2020-15842 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-15842 and fix it if it is affected. What it is: CVE-2020-15842 is a high-severity unsafe deserialization vulnerability in Liferay Digital Experience Platform, published on 20 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2020-15842 in the wild and no public exploit code. Affected packages and fixed versions: - com.liferay.portal:release.dxp.bom (Maven): affected from 7.0.0; fixed in 7.0.10.fp90 - com.liferay.portal:release.dxp.bom (Maven): affected from 7.0.0; fixed in 7.0.10.fp90 - com.liferay.portal:release.dxp.bom (Maven): affected from 7.1.0; fixed in 7.1.10.fp17 - com.liferay.portal:release.dxp.bom (Maven): affected from 7.1.0; fixed in 7.1.10.fp17 - com.liferay.portal:release.dxp.bom (Maven): affected from 7.2.0; fixed in 7.2.10.fp5 - com.liferay.portal:release.dxp.bom (Maven): affected from 7.2.0; fixed in 7.2.10.fp5 - com.liferay.portal:release.portal.bom (Maven): affected all versions; fixed in 7.3.0 - com.liferay.portal:release.portal.bom (Maven): affected all versions; fixed in 7.3.0 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-15842/ (Markdown: https://insights.sbomify.com/CVE-2020-15842/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-15842 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-15842 - OSV: https://osv.dev/vulnerability/CVE-2020-15842 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-15842/ Summaries are generated and may contain mistakes; the official description above is the record.