# CVE-2010-2944: Auth bypass in n/a

> Remote attackers can gain privileges by bypassing password verification for the emergency account in the Zope LDAPUserFolder library.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Aug 2010
- **Updated:** 16 Sep 2024
- **Also known as:** DSA-2096-1, GHSA-9593-96fp-8w9m

## What is CVE-2010-2944?

CVE-2010-2944 is a high-severity authentication bypass vulnerability in n/a, published on 20 Aug 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The authenticate function in LDAPUserFolder/LDAPUserFolder.py in zope-ldapuserfolder 2.9-1 does not verify the password for the emergency account, which allows remote attackers to gain privileges.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2010-2944?

It affects 1 product.


Products: Jens Vagelpohl Zope-Ldapuserfolder.

## How do I fix CVE-2010-2944?

Apply the vendor's patch.

## Is CVE-2010-2944 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-2944 and fix it if it is affected.

What it is: CVE-2010-2944 is a high-severity authentication bypass vulnerability in n/a, published on 20 Aug 2010. 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-2010-2944 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-2010-2944/ (Markdown: https://insights.sbomify.com/CVE-2010-2944/index.md)
```

## Sources

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

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