# CVE-2022-42132: Liferay Portal and Liferay DXP Includes LDAP Credentials in the Page URL > Attackers can view LDAP credentials in page URLs during user pagination, exposing sensitive authentication data to man-in-the-middle attackers or log access. - **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 15 Nov 2022 - **Updated:** 9 Jul 2026 - **Also known as:** BIT-liferay-2022-42132, GHSA-f43m-hhj4-q3jg ## What is CVE-2022-42132? CVE-2022-42132 is a medium-severity vulnerability in Liferay Digital Experience Platform, published on 15 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description The Test LDAP Users functionality in Liferay Portal 7.0.0 through 7.4.3.4, and Liferay DXP 7.0 fix pack 102 and earlier, 7.1 before fix pack 27, 7.2 before fix pack 17, 7.3 before update 4, and DXP 7.4 GA includes the LDAP credential in the page URL when paginating through the list of users, which allows man-in-the-middle attackers or attackers with access to the request logs to see the LDAP credential. Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2022-42132? 15 open source packages ship an affected version, including com.liferay.portal:release.dxp.bom, liferay and com.liferay.portal:release.portal.bom. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `com.liferay.portal:release.dxp.bom` | Maven | All versions | None | | `com.liferay.portal:release.dxp.bom` | Maven | All versions | None | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.0.0 to 7.0.10.fp102 | None | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.0.0 to 7.0.10.fp102 | None | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.1.0 | 7.1.10.fp27 | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.1.0 | 7.1.10.fp27 | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.2.0 | 7.2.10.fp17 | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.2.0 | 7.2.10.fp17 | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.3.0 | 7.3.10.u4 | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.3.0 | 7.3.10.u4 | | `liferay` | Bitnami | From 7.0.0 to 7.0.0 | None | | `com.liferay.portal:release.portal.bom` | Maven | From 7.0.0 | 7.4.3.5-ga5 | | `com.liferay.portal:release.portal.bom` | Maven | From 7.0.0 | 7.4.3.5-ga5 | | `com.liferay:com.liferay.portal.settings.authentication.ldap.web` | Maven | All versions | 5.0.13 | | `com.liferay:com.liferay.portal.settings.authentication.ldap.web` | Maven | All versions | 5.0.13 | Products: Liferay Digital Experience Platform, Liferay Liferay Portal. ## How do I fix CVE-2022-42132? Upgrade com.liferay.portal:release.dxp.bom to a fixed version for your release line: 7.1.10.fp27, 7.2.10.fp17 or 7.3.10.u4. ## Is CVE-2022-42132 being exploited? There is no known exploitation of CVE-2022-42132 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-2022-42132 and fix it if it is affected. What it is: CVE-2022-42132 is a medium-severity vulnerability in Liferay Digital Experience Platform, published on 15 Nov 2022. 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-2022-42132 in the wild and no public exploit code. Affected packages and fixed versions: - com.liferay.portal:release.dxp.bom (Maven): affected all versions; no fix listed - com.liferay.portal:release.dxp.bom (Maven): affected all versions; no fix listed - com.liferay.portal:release.dxp.bom (Maven): affected from 7.0.0 up to 7.0.10.fp102; no fix listed - com.liferay.portal:release.dxp.bom (Maven): affected from 7.0.0 up to 7.0.10.fp102; no fix listed - com.liferay.portal:release.dxp.bom (Maven): affected from 7.1.0; fixed in 7.1.10.fp27 - com.liferay.portal:release.dxp.bom (Maven): affected from 7.1.0; fixed in 7.1.10.fp27 - com.liferay.portal:release.dxp.bom (Maven): affected from 7.2.0; fixed in 7.2.10.fp17 - com.liferay.portal:release.dxp.bom (Maven): affected from 7.2.0; fixed in 7.2.10.fp17 - com.liferay.portal:release.dxp.bom (Maven): affected from 7.3.0; fixed in 7.3.10.u4 - com.liferay.portal:release.dxp.bom (Maven): affected from 7.3.0; fixed in 7.3.10.u4 - liferay (Bitnami): affected from 7.0.0 up to 7.0.0; no fix listed - com.liferay.portal:release.portal.bom (Maven): affected from 7.0.0; fixed in 7.4.3.5-ga5 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-2022-42132/ (Markdown: https://insights.sbomify.com/CVE-2022-42132/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-42132 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-42132 - OSV: https://osv.dev/vulnerability/CVE-2022-42132 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-42132/ Summaries are generated and may contain mistakes; the official description above is the record.