# CVE-2005-2069: Weak cryptography in n/a

> Remote attackers can sniff passwords sent in cleartext when pam_ldap or nss_ldap fails to use TLS for referrals to master servers.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/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:** Yes
- **Published:** 29 Jun 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-2069, GHSA-fv7v-76vm-38q4

## What is CVE-2005-2069?

CVE-2005-2069 is a medium-severity vulnerability in n/a, published on 29 Jun 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

pam_ldap and nss_ldap, when used with OpenLDAP and connecting to a slave using TLS, does not use TLS for the subsequent connection if the client is referred to a master, which may cause a password to be sent in cleartext and allows remote attackers to sniff the password.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2005-2069?

It affects 2 products.


Products: Padl Nss Ldap, Padl Pam Ldap.

## How do I fix CVE-2005-2069?

Apply the vendor's patch.

## Is CVE-2005-2069 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2069 and fix it if it is affected.

What it is: CVE-2005-2069 is a medium-severity vulnerability in n/a, published on 29 Jun 2005. 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-2005-2069 in the wild and no public exploit code.

Affected product: n/a. 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-2005-2069/ (Markdown: https://insights.sbomify.com/CVE-2005-2069/index.md)
```

## Sources

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

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