# CVE-2003-0734: Auth bypass in n/a

> Attackers can bypass host-based access restrictions to log onto systems using pam_ldap with LDAP authentication.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 4 Sep 2003
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2003-0734, GHSA-5p76-qmmf-h53v

## What is CVE-2003-0734?

CVE-2003-0734 is a critical authentication bypass vulnerability in n/a, published on 4 Sep 2003. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unknown vulnerability in the pam_filter mechanism in pam_ldap before version 162, when LDAP based authentication is being used, allows users to bypass host-based access restrictions and log onto the system.

## Which versions are affected by CVE-2003-0734?

It affects 1 product.


Products: Padl Software Pam Ldap.

## How do I fix CVE-2003-0734?

Upgrade to a fixed version.

## Is CVE-2003-0734 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-2641](https://insights.sbomify.com/CVE-2005-2641/): Privilege escalation in n/a (high 7.5)
- [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-2003-0734 and fix it if it is affected.

What it is: CVE-2003-0734 is a critical authentication bypass vulnerability in n/a, published on 4 Sep 2003. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2003-0734 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-2003-0734/ (Markdown: https://insights.sbomify.com/CVE-2003-0734/index.md)
```

## Sources

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

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