# CVE-2022-41414: Liferay Portal Insecure Default Configuration in auth.login.prompt.enabled

> Attackers can enumerate usernames, site names, and pages due to an insecure default configuration in Liferay Portal.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 7 Oct 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-9427-7f65-88c8

## What is CVE-2022-41414?

CVE-2022-41414 is a medium-severity vulnerability in Liferay Liferay Portal, published on 7 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An insecure default in the component auth.login.prompt.enabled of Liferay Portal v7.0.0 through v7.4.2 allows attackers to enumerate usernames, site names, and pages.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2022-41414?

4 open source packages ship an affected version, including com.liferay.portal:com.liferay.portal.impl and com.liferay.portal:release.portal.bom. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.liferay.portal:com.liferay.portal.impl` | Maven | All versions | 8.0.0 |
| `com.liferay.portal:com.liferay.portal.impl` | Maven | All versions | 8.0.0 |
| `com.liferay.portal:release.portal.bom` | Maven | From 7.0.0-a1 | 7.4.2-ga3 |
| `com.liferay.portal:release.portal.bom` | Maven | From 7.0.0-a1 | 7.4.2-ga3 |

Products: Liferay Liferay Portal.

## How do I fix CVE-2022-41414?

Upgrade com.liferay.portal:com.liferay.portal.impl to 8.0.0 or later.

## Is CVE-2022-41414 being exploited?

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

## Other vulnerabilities in Liferay Liferay Portal

- [CVE-2020-7961](https://insights.sbomify.com/CVE-2020-7961/): Liferay Portal Deserialization of Untrusted Data (critical 9.8, exploited in the wild)
- [CVE-2021-33990](https://insights.sbomify.com/CVE-2021-33990/): File upload in n/a (critical 9.8)
- [CVE-2019-16891](https://insights.sbomify.com/CVE-2019-16891/): Liferay Portal Allows RCE via Deserialization of a JSON Payload (critical 9.8)
- [CVE-2023-47797](https://insights.sbomify.com/CVE-2023-47797/): Liferay Portal XSS with `p_l_back_url_title` on edit content page (critical 9.6)
- [CVE-2020-13445](https://insights.sbomify.com/CVE-2020-13445/): Liferay Portal and Liferay DXP Vulnerable to Arbitrary Code Execution (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41414 and fix it if it is affected.

What it is: CVE-2022-41414 is a medium-severity vulnerability in Liferay Liferay Portal, published on 7 Oct 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-41414 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.liferay.portal:com.liferay.portal.impl (Maven): affected all versions; fixed in 8.0.0
- com.liferay.portal:com.liferay.portal.impl (Maven): affected all versions; fixed in 8.0.0
- com.liferay.portal:release.portal.bom (Maven): affected from 7.0.0-a1; fixed in 7.4.2-ga3
- com.liferay.portal:release.portal.bom (Maven): affected from 7.0.0-a1; fixed in 7.4.2-ga3

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

## Sources

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

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