dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2022-42132

MEDIUM · 5.9 CVSS v3.1 Published 2022-11-15
Fix available
A fix is available. Upgrade to 7.4.3.5 or later.
See remediation →
68/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 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.

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

The Test LDAP Users functionality in Liferay Portal and DXP embeds LDAP bind credentials in URL query parameters during pagination of user lists. This exposes sensitive authentication credentials through URLs that get logged in server access logs, browser history, and proxy logs, enabling credential harvesting by attackers with log access.

MitigationUpgrade to Lifer DXP 7.1 fix pack 27+, 7.2 fix pack 17+, 7.3 update 4+, 7.4.3.5+, or DXP 7.4 GA+. Additionally, audit request logs for exposed LDAP credentials and consider credential rotation as a precautionary measure.

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.0= 7.1= 7.2= 7.3= 7.4
Liferay PortalApplication
Affected:>= 7.0.0, < 7.4.3.5

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/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 Lifter Portal/DXP version
    Check the deployed Lifer installation's version. This is typically visible in the Control Panel, in the product footer, or in the osgi/state directory. Compare against affected ranges: DXP 7.0-7.4 or Portal 7.0.0 to 7.4.3.4.
    Affected if The installed version falls within 7.0 through 7.4.4 (or below 7.4.3.5 for Portal)
  2. Verify LDAP is configured
    In Lifer admin Control Panel, navigate to Configuration > Instance Settings > Authentication > LDAP. Check if any LDAP directories are enabled and connected.
    Affected if LDAP authentication or directory integration is enabled with at least one LDAP server configured
  3. Confirm Test LDAP Users functionality exists
    Locate the Test LDAP Users feature in Lifer Control Panel under Configuration > LDAP. This feature is used to test LDAP user imports and displays results with pagination.
    Affected if The Test LDAP Users or LDAP Import test feature is present and accessible in the Control Panel
  4. Audit server access logs for exposed credentials
    Review HTTP access logs from the application server (Tomcat, WildFly, etc.), reverse proxy, or load balancer. Search for GET requests to LDAP test pages containing query parameters with values resembling passwords (base64 strings, special characters in URL parameters).
    Affected if Access logs contain URLs with LDAP bind credentials or sensitive parameters in the query string

Environment is affected if running a vulnerable Lifer version with LDAP enabled and the Test LDAP Users feature accessible, especially if URL logs show credential exposure.

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.5 or later
Fixed in 7.4.3.5
Interim mitigation

Upgrade to Lifer DXP 7.1 fix pack 27+, 7.2 fix pack 17+, 7.3 update 4+, 7.4.3.5+, or DXP 7.4 GA+. Additionally, audit request logs for exposed LDAP credentials and consider credential rotation as a precautionary measure.

Recommended fix High confidence

LPortal 7.4.3.5+ or DXP fix pack 103+/27+/17+/update 4+ depending on version

  1. 1. Identify your current LPortal/DXP version and edition (Portal or DXP)
  2. 2. For LPortal 7.0.0-7.4.3.4: Upgrade to LPortal 7.4.3.5 or later
  3. 3. For DXP 7.0: Apply fix pack 103 or later
  4. 4. For DXP 7.1: Apply fix pack 27 or later
  5. 5. For DXP 7.2: Apply fix pack 17 or later
  6. 6. For DXP 7.3: Apply update 4 or later
  7. 7. After upgrade, verify the Test LDAP Users pagination no longer includes credentials in URLs
  8. 8. Review access logs to ensure no credentials were previously exposed
Caveat Fix packs may include other changes; review Liferays release notes for your specific version for potential compatibility issues

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

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-42132 — 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-42132 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