# CVE-2002-0735: Other in n/a

> Remote attackers can cause denial of service or execute arbitrary code via format string vulnerability in Squid LDAP authentication module logging.

- **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:** No
- **Published:** 26 Jul 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-g6h3-4wm6-7hpq

## What is CVE-2002-0735?

CVE-2002-0735 is a high-severity vulnerability in n/a, published on 26 Jul 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Format string vulnerability in the logging() function in C-Note Squid LDAP authentication module (squid_auth_LDAP) 2.0.2 and earlier allows remote attackers to cause a denial of service and possibly execute arbitrary code by triggering log messages.

## Which versions are affected by CVE-2002-0735?

It affects 3 products.


Products: C-Note Squid Auth Ldap, Padl Software Nss Ldap, Padl Software Pam Ldap.

## How do I fix CVE-2002-0735?

No fix has been published for CVE-2002-0735 yet. Limit exposure of the affected software until one is available.

## Is CVE-2002-0735 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-0735 and fix it if it is affected.

What it is: CVE-2002-0735 is a high-severity vulnerability in n/a, published on 26 Jul 2002. 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-2002-0735 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-2002-0735/ (Markdown: https://insights.sbomify.com/CVE-2002-0735/index.md)
```

## Sources

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

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