CVE-2023-4501: Authentication bypass in OpenText (Micro Focus) Enterprise Server
User authentication with username and password credentials is ineffective in OpenText (Micro Focus) Visual COBOL, COBOL Server, Enterprise Developer, and Enterprise Server (including product variants such as Enterprise Test Server), versions 7.0 patch updates 19 and 20, 8.0 patch updates 8 and 9, and 9.0 patch update 1, when LDAP-based authentication is used with certain configurations. When the vulnerability is active, authentication succeeds with any valid username, regardless of whether the password is correct; it may also succeed with an invalid username (and any password). This allows an attacker with access to the product to impersonate any user.
Mitigations: The issue is corrected in the upcoming patch update for each affected product. Product overlays and workaround instructions are available through OpenText Support. The vulnerable configurations are believed to be uncommon.
Administrators can test for the vulnerability in their installations by attempting to sign on to a Visual COBOL or Enterprise Server component such as ESCWA using a valid username and incorrect password.
Security readout for executives and security teams
Plain-English summary
Affected OpenText COBOL and Enterprise Server products may accept incorrect passwords in certain LDAP configurations. An attacker who can reach the product could impersonate users, potentially gaining access to sensitive applications and data. OpenText believes vulnerable configurations are uncommon, but exposed installations require urgent verification.
Executive priority
Treat as an urgent exposure-validation issue because successful bypass could enable full user impersonation and major business impact. Immediately identify affected LDAP deployments, restrict access, and engage OpenText Support. Prioritize confirmed-vulnerable or externally reachable systems for remediation.
Technical view
CVE-2023-4501 is an authentication bypass affecting specified 7.0, 8.0, and 9.0 patch updates when LDAP authentication uses certain configurations. Authentication may accept any password for a valid username and may accept invalid usernames. The CVSS 3.1 score is 9.8, reflecting network-reachable, unauthenticated compromise with potentially severe confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to the named OpenText products and patch updates using affected LDAP configurations. OpenText believes these configurations are uncommon. Risk is greatest where product interfaces are reachable by untrusted networks or users. The supplied evidence does not identify the exact configuration conditions.
Exploitation context
The supplied record does not establish active exploitation, and the CVE is not identified as being in CISA KEV. Exploitation requires access to an affected product interface, but no prior authentication, user interaction, or correct password is required when the vulnerable configuration is active.
Researcher notes
The record maps the weakness to authentication and credential-validation CWEs 253, 287, 305, and 358. Named affected levels include 7.0 patch updates 19 and 20, 8.0 updates 8 and 9, and 9.0 update 1. Exact triggering LDAP configurations and forensic indicators are not provided.
Mitigation direction
Inventory the named products, patch-update levels, LDAP usage, and externally reachable management interfaces.
Obtain the applicable corrective patch update, overlay, and workaround instructions from OpenText Support.
Apply vendor-provided corrections according to OpenText guidance and organizational change controls.
Restrict affected interfaces to trusted administrators and networks until vendor remediation is applied.
Validation and detection
Attempt an authorized sign-on using a valid username and deliberately incorrect password.
Treat any successful incorrect-password sign-on as evidence that the vulnerable condition is active.
Confirm corrected systems reject invalid credentials across each relevant component, including ESCWA.
Review authentication logs for unexpected successful sign-ons, while recognizing logs alone cannot prove absence of exploitation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-253: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
6Timeline events
2ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.