CVE-2022-41414
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAn insecure default in Liferay Portal's auth.login.prompt.enabled setting (enabled by default in v7.0.0 through v7.4.2) allows unauthenticated attackers to probe the login endpoint and receive different responses for valid vs invalid usernames, as well as enumerate site names and page existence, facilitating credential stuffing and targeted attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 7.0.0, <= 7.4.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Lifaxer Portal versionCheck the portal version through the Control Panel (Control Panel > Configuration > Server Administration > Product Information) or by inspecting the portal-version property in portal-ext.properties or the OSGi bundle metadataAffected if The installed version falls within >= 7.0.0 and <= 7.4.2
-
Locate the auth.login.prompt.enabled configurationInspect portal-ext.properties, portal-setup-wizard.properties, or the LMTP Control Panel under System Settings > Security > Auth > General to find the auth.login.prompt.enabled property settingAffected if The property is set to true or not explicitly set (using the insecure default)
-
Test login endpoint response behaviorSend two POST requests to /c/portal/login with identical passwords but different usernames (one known-valid, one random). Compare the HTTP response status codes, error messages, or response times between the two requestsAffected if The endpoint returns distinctly different responses (e.g., different error messages, HTTP 200 vs 401, or different response bodies) for valid vs invalid usernames, confirming user enumeration is possible
A Lifer Portal installation is affected if it runs version 7.0.0 through 7.4.2 and has auth.login.prompt.enabled set to true (or unset, relying on the insecure default), allowing the login endpoint to be probed for user enumeration.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataDisable the auth.login.prompt.enabled property in portal-ext.properties or via the LMTP Control Panel, and implement rate limiting on authentication endpoints to prevent automated enumeration.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41414 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-41414 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data