Security readout for executives and security teams
Plain-English summary
A ForgeRock LDAP Connector flaw can allow access without valid authentication when StartTLS is configured. Because the connector is bundled with IDM and Remote Connector Server, identity infrastructure using those components may be exposed. The main business risk is unauthorized access to identity-managed systems and sensitive directory-linked data.
Executive priority
Treat this as urgent for identity environments because authentication bypass in a connector can undermine access controls. Prioritize internet- or partner-reachable deployments first, then internal identity infrastructure using StartTLS. Remediation should be tracked as a critical identity-security item.
Technical view
CVE-2022-0143 is a CWE-284 improper access control issue in ForgeRock LDAP Connector versions before 1.5.20.9. With StartTLS configured, the connector may ignore an incorrect password and grant unauthenticated access. CVSS 3.1 is 9.3 with network attack vector, low complexity, no privileges required, user interaction required, and high confidentiality and integrity impact.
Likely exposure
Organizations using ForgeRock LDAP Connector before 1.5.20.9 are the relevant exposure group, including deployments bundled with ForgeRock IDM or Remote Connector Server. Exposure is most urgent where StartTLS is enabled and connector endpoints are reachable over a network.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. The CVSS vector indicates remote reachability, low complexity, no required privileges, and required user interaction. Treat exposed StartTLS-enabled connector deployments as high-priority until version and configuration are verified.
Researcher notes
Evidence is limited to the CVE record and ForgeRock references in the bundle. The key condition is StartTLS use with LDAP Connector versions before 1.5.20.9. Do not assume exploitation or additional affected products without vendor evidence.
Mitigation direction
- Identify all ForgeRock LDAP Connector deployments, including IDM and Remote Connector Server bundles.
- Upgrade affected LDAP Connector installations to version 1.5.20.9 or follow current ForgeRock guidance.
- Prioritize systems with StartTLS enabled and network-reachable connector services.
- Restrict network access to connector services while remediation is pending.
- Review authentication logs for unexpected successful access involving invalid or failed credential attempts.
Validation and detection
- Confirm deployed LDAP Connector versions are 1.5.20.9 or not affected per ForgeRock guidance.
- Check whether StartTLS is configured on each LDAP Connector deployment.
- Map connector exposure from IDM and Remote Connector Server hosts.
- Verify connector services are not broadly reachable from untrusted networks.
- Review recent identity and LDAP access logs for anomalous authentication outcomes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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.
Open ATT&CK lookupCredential and access behavior lookup
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.
Open ATT&CK lookupCVE-2022-0143 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N2.85.8Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.3CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.