dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2022-42127

MEDIUM · 5.3 CVSS v3.1 Published 2022-11-15
Fix available
A fix is available. Upgrade to 7.4.3.37 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
The Friendly Url module in Liferay Portal 7.4.3.5 through 7.4.3.36, and Liferay DXP 7.4 update 1 though 36 does not properly check user permissions, which allows remote attackers to obtain the history of all friendly URLs that was assigned to a page.

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 confidence

This is an Insecure Direct Object Reference (IDOR) vulnerability in Liferay Portal and DXP's Friendly URL module. The module fails to enforce proper authorization checks when accessing the friendly URL history for a page, allowing unauthenticated remote attackers to enumerate all historical friendly URLs assigned to any page in the system.

MitigationApply the vendor patch for CVE-2022-42127 to Liferay Portal 7.4.3.5+ or Liferay DXP 7.4 update 1+. If patching is not immediately possible, restrict network access to the portal and review access controls on page-level operations.

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
Digital Experience PlatformApplication
Affected:= 7.4
Liferay PortalApplication
Affected:>= 7.4.3.5, < 7.4.3.37

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Lifer Portal or DXP version
    Check the Lifer Portal or DXP version by examining the portal.properties file, the Lifer Portal control panel (Server Information), or the OSGi bundle version in the Lifer Marketplace. The version is typically displayed in the Control Panel under Configuration > Server Administration.
    Affected if The installed version is Lifer DXP 7.4 (any version) or Lifer Portal >= 7.4.3.5 and < 7.4.3.37
  2. Confirm Friendly URL module is accessible
    Verify that the Friendly URL module (com_lifer_portalFriendlyURL) is deployed and active in the OSGi console (accessible via /o/system/console/bundles) or check that the friendly URL servlet mapping is available in the web.xml.
    Affected if The Friendly URL module is loaded and the friendly URL servlet is exposed without additional authentication requirements.
  3. Test unauthenticated access to URL history endpoint
    Send an HTTP GET request to a known page's friendly URL history endpoint. Typical patterns include endpoints like /friendly-url-history or /api/jsonws/invoke with FriendlyURLHistory related methods. No authentication headers should be provided in the request.
    Affected if The response returns historical friendly URL data for pages without requiring authentication or valid session credentials.
  4. Verify authorization on cross-page URL history requests
    Using an unauthenticated or low-privileged session, attempt to access the friendly URL history for multiple different page IDs (such as /c/portal/friendly_url_history?p_l_id=PAGE_ID for various page IDs).
    Affected if The system returns friendly URL history for pages other than those the current user owns or has permission to access, indicating missing authorization checks.

A Lifer Portal or DXP installation is affected if it is version 7.4 (DXP) or between 7.4.3.5 and 7.4.3.37 (Portal) AND the Friendly URL history endpoint is accessible to unauthenticated users or returns data for pages the requester should not access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 7.4.3.37 or later
Fixed in 7.4.3.37
Interim mitigation

Apply the vendor patch for CVE-2022-42127 to Liferay Portal 7.4.3.5+ or Liferay DXP 7.4 update 1+. If patching is not immediately possible, restrict network access to the portal and review access controls on page-level operations.

Recommended fix High confidence

Liferay Portal 7.4.3.37+ or Liferay DXP 7.4 Update 37+

  1. Backup your current Linstallation before upgrading
  2. Upgrade Liferay Portal to version 7.4.3.37 or later, or upgrade Liferay DXP to update 37 or later
  3. After upgrading, verify that the FriendlyUrl module is functioning correctly
  4. Test that proper permission checks are now enforced for accessing friendly URL history
Caveat Standard Lminor version upgrade - review release notes for any breaking changes, especially related to permissions or FriendlyUrl module

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-42127 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-42127 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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