Security Bulletin: LDAP vulnerability in WebSphere Liberty Profile can affect IBM InfoSphere Global Name Management ENS (CVE-2021-39031)

Summary

A vulnerability in the WebSphere Liberty Profile used in IBM InfoSphere Global Name Management (GNM) Enterprise Name Service (ENS) could allow a remote authenticated attacker to conduct an LDAP injection. This issue only affects ENS, a part of GNM installed by a small minority of GNM customers. For customers using ENS, the vulnerability only exists if the installation uses LDAP, which would only happen as a result of manual configuration changes made by the customer to the WebSphere Liberty within ENS. ENS as installed does not configure LDAP. For GNM customers not using ENS, and for ENS customers not configuring LDAP, there is no vulnerability.

Vulnerability Details

CVEID:CVE-2021-39031
**DESCRIPTION:**IBM WebSphere Application Server - Liberty 17.0.0.3 through 22.0.0.1 could allow a remote authenticated attacker to conduct an LDAP injection. By using a specially crafted request, an attacker could exploit this vulnerability and could result in in granting permission to unauthorized resources. IBM X-Force ID: 213875.
CVSS Base score: 7.5
CVSS Temporal Score: See: https://exchange.xforce.ibmcloud.com/vulnerabilities/213875 for the current score.
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H)

Affected Products and Versions

Remediation/Fixes

Per the original bulletin for CVE-2021-39031 (<https://www.ibm.com/support/pages/security-bulletin-ibm-websphere-application-server-liberty-vulnerable-ldap-injection-cve-2021-39031&gt;), update WebSphere Liberty Profile to version 22.0.0.2 or later.

GNM version 6 customers using Enterprise Name Search (a separate installation from regular GNM, and one which does not apply to most customers) can update ENS using the files and instructions in GNM 6 interim fix 13, available at IBM Fix Central. This updates the WebSphere Liberty in ENS to version 22.0.0.3.

For non-ENS GNM users and for ENS customers not configuring LDAP, there is no vulnerability and no remediation is required.

Workarounds and Mitigations

None