# CVE-2006-0150: Memory corruption in n/a

> Remote attackers can execute arbitrary code via format string vulnerabilities in the Apache auth_ldap module's logging function.

- **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:** 9 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-952-1, GHSA-9gq6-2mjq-v47h

## What is CVE-2006-0150?

CVE-2006-0150 is a high-severity memory corruption vulnerability in n/a, published on 9 Jan 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple format string vulnerabilities in the auth_ldap_log_reason function in Apache auth_ldap 1.6.0 and earlier allows remote attackers to execute arbitrary code via various vectors, including the username.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

## Which versions are affected by CVE-2006-0150?

It affects 1 product.


Products: Dave Carrigan Auth Ldap.

## How do I fix CVE-2006-0150?

Upgrade to a fixed version.

## Is CVE-2006-0150 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-0150 and fix it if it is affected.

What it is: CVE-2006-0150 is a high-severity memory corruption vulnerability in n/a, published on 9 Jan 2006. 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-2006-0150 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-2006-0150/ (Markdown: https://insights.sbomify.com/CVE-2006-0150/index.md)
```

## Sources

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

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