GHSA-773f-f929-qgjj CVE-2020-15841
Liferay Portal and Liferay DXP Potentially Reveal LDAP Server Password via Unsafe Connection
- Severity
- 8.3 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 1.51%
- Chance of exploitation in the next 30 days. Higher than 74.50% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-522 Insufficiently Protected Credentials
- Fix
- Available
- 2 packages have a fixed version
Description
Liferay Portal before 7.3.0, and Liferay DXP 7.0 before fix pack 89, 7.1 before fix pack 17, and 7.2 before fix pack 4, does not safely test a connection to a LDAP server, which allows remote attackers to obtain the LDAP server's password via the Test LDAP Connection feature.
Affected versions
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| com.liferay.portal:release.dxp.bom | >= 7.0.0, < 7.0.10.fp89 |
7.0.10.fp89 |
| com.liferay.portal:release.dxp.bom | >= 7.1.0, < 7.1.10.fp17 |
7.1.10.fp17 |
| com.liferay.portal:release.dxp.bom | >= 7.2.0, < 7.2.10.fp4 |
7.2.10.fp4 |
| com.liferay.portal:release.portal.bom | < 7.3.0 |
7.3.0 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
com.liferay.portal:release.dxp.bom Maven → 7.0.10.fp89
- maven
<dependency><groupId>com.liferay.portal</groupId><artifactId>release.dxp.bom</artifactId><version>7.0.10.fp89</version></dependency>- gradle
implementation("com.liferay.portal:release.dxp.bom:7.0.10.fp89")
com.liferay.portal:release.portal.bom Maven → 7.3.0
- maven
<dependency><groupId>com.liferay.portal</groupId><artifactId>release.portal.bom</artifactId><version>7.3.0</version></dependency>- gradle
implementation("com.liferay.portal:release.portal.bom:7.3.0")
Severity breakdown
CVSS 3.1 8.3
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Weakness
CWE-522: Insufficiently Protected Credentials
The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.
How to prevent it
- Architecture and Design: Use an appropriate security mechanism to protect the credentials.
- Architecture and Design: Make appropriate use of cryptography to protect the credentials.
- Implementation: Use industry standards to protect the credentials (e.g. LDAP, keystore, etc.).
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-2j97-4jmq-c4xf Liferay Portal Vulnerable to Reflected XSS via the selectedLanguageId Parameter | Medium | Also affects com.liferay.portal:release.portal.bom |
| GHSA-56jv-4ww3-65mw Liferay Portal is vulnerable to XSS in the Blogs widget | Medium | Also affects com.liferay.portal:release.portal.bom |
| GHSA-f5vh-4rj2-w8r8 Liferay Portal is vulnerable to DNS rebinding attacks | Medium | Also affects com.liferay.portal:release.portal.bom |
| GHSA-8hw3-ghwv-crfh Liferay Portal vulnerable to password enumeration | Medium | Also affects com.liferay.portal:release.portal.bom |
| GHSA-gv7w-jh8g-vr73 Liferay Portal Does Not Limit Access to APIs Before Email Verification | Medium | Also affects com.liferay.portal:release.portal.bom |
| GHSA-gh4w-8qgq-8w9r Liferay Portal Vulnerable to CSRF in Headless APIs | Medium | Also affects com.liferay.portal:release.portal.bom |
| GHSA-xcj6-xpjg-c4xr Liferay Portal Stores Password Reset Tokens in Plain Text | Medium | Also affects com.liferay.portal:release.portal.bom |
| GHSA-vgqx-447m-wvcj Liferay Portal Vulnerable to DoS via Crafted Headless API Request | High | Also affects com.liferay.portal:release.portal.bom |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor