# CVE-2005-2641: Privilege escalation in n/a

> Attackers can gain privileges by exploiting improper handling of password policy controls in the pam_ldap module.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Aug 2005
- **Updated:** 7 Aug 2024
- **Also known as:** CVE-2005-2497, DEBIAN-CVE-2005-2641, GHSA-f3wv-7jx9-8mxj

## What is CVE-2005-2641?

CVE-2005-2641 is a high-severity vulnerability in n/a, published on 21 Aug 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unknown vulnerability in pam_ldap before 180 does not properly handle a new password policy control, which could allow attackers to gain privileges.  NOTE: CVE-2005-2497 had also been assigned to this issue, but CVE-2005-2641 is the correct candidate.

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

It affects 1 product.


Products: Padl Software Pam Ldap.

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

Upgrade to a fixed version.

## Is CVE-2005-2641 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0734](https://insights.sbomify.com/CVE-2003-0734/): Auth bypass in n/a (critical 10.0)
- [CVE-2002-0374](https://insights.sbomify.com/CVE-2002-0374/): Other in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-2641 is a high-severity vulnerability in n/a, published on 21 Aug 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-2641 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-2641/ (Markdown: https://insights.sbomify.com/CVE-2005-2641/index.md)
```

## Sources

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

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