# CVE-2020-4129: Security feature bypass in HCL Domino

> An unauthenticated attacker can bypass lockout policies in HCL Domino LDAP to perform brute force attacks.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-qmmq-6cfg-qc67

## What is CVE-2020-4129?

CVE-2020-4129 is a medium-severity vulnerability in HCL Domino, published on 30 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HCL Domino is susceptible to a lockout policy bypass vulnerability in the LDAP service. An unauthenticated attacker could use this vulnerability to mount a brute force attack against the LDAP service. Fixes are available in HCL Domino versions 9.0.1 FP10 IF6, 10.0.1 FP6 and 11.0.1 FP1 and later.

## Which versions are affected by CVE-2020-4129?

It affects 1 product.


Products: Hcltech Hcl Domino.

## How do I fix CVE-2020-4129?

No fix has been published for CVE-2020-4129 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-4129 being exploited?

There is no known exploitation of CVE-2020-4129 in the wild and no public exploit code.

## Other vulnerabilities in HCL Domino

- [CVE-2020-4127](https://insights.sbomify.com/CVE-2020-4127/): Cross-site request forgery in HCL Domino (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-4129 and fix it if it is affected.

What it is: CVE-2020-4129 is a medium-severity vulnerability in HCL Domino, published on 30 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-4129 in the wild and no public exploit code.

Affected product: HCL Domino. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-4129/ (Markdown: https://insights.sbomify.com/CVE-2020-4129/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-4129
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-4129
- OSV: https://osv.dev/vulnerability/CVE-2020-4129

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-4129/
Summaries are generated and may contain mistakes; the official description above is the record.