# CVE-2022-24832: Bundled ldap-authentication-plugin fails to neutralise LDAP special elements in usernames

> An authenticated user can exploit LDAP injection in the bundled plugin to deduce sensitive information about other LDAP entries via brute force.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Apr 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-x5v3-x9qj-mh3h

## What is CVE-2022-24832?

CVE-2022-24832 is a high-severity vulnerability in gocd, published on 11 Apr 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

GoCD is an open source a continuous delivery server. The bundled gocd-ldap-authentication-plugin included with the GoCD Server fails to correctly escape special characters when using the username to construct LDAP queries. While this does not directly allow arbitrary LDAP data exfiltration, it can allow an existing LDAP-authenticated GoCD user with malicious intent to construct and execute malicious queries, allowing them to deduce facts about other users or entries within the LDAP database (e.g alternate fields, usernames, hashed passwords etc) through brute force mechanisms. This only affects users who have a working LDAP authorization configuration enabled on their GoCD server, and only is exploitable by users authenticating using such an LDAP configuration. This issue has been fixed in GoCD 22.1.0, which is bundled with gocd-ldap-authentication-plugin v2.2.0-144.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2022-24832?

It affects 1 product.


Products: Thoughtworks Gocd.

## How do I fix CVE-2022-24832?

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

## Is CVE-2022-24832 being exploited?

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

## Other vulnerabilities in gocd

- [CVE-2021-43290](https://insights.sbomify.com/CVE-2021-43290/): Path traversal in n/a (critical 9.8)
- [CVE-2021-44659](https://insights.sbomify.com/CVE-2021-44659/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2024-56320](https://insights.sbomify.com/CVE-2024-56320/): GoCD vulnerable to admin privilege escalation by a malicious internal/existing authenticated user (critical 9.4)
- [CVE-2022-39311](https://insights.sbomify.com/CVE-2022-39311/): Compromised agents may be able to execute remote code on GoCD Server (critical 9.1)
- [CVE-2022-29184](https://insights.sbomify.com/CVE-2022-29184/): Command Injection/Argument Injection in GoCD (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-24832 and fix it if it is affected.

What it is: CVE-2022-24832 is a high-severity vulnerability in gocd, published on 11 Apr 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-24832 in the wild and no public exploit code.

Affected product: gocd. 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-2022-24832/ (Markdown: https://insights.sbomify.com/CVE-2022-24832/index.md)
```

## Sources

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

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