# CVE-2002-1508: Race condition in n/a

> Local attackers can overwrite arbitrary files via a race condition in OpenLDAP's replication log creation, potentially compromising system integrity.

- **Severity:** Low 1.2 (`AV:L/AC:H/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Feb 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-97gv-8325-5xwj

## What is CVE-2002-1508?

CVE-2002-1508 is a low-severity vulnerability in Openldap Openldap, published on 11 Feb 2003. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

slapd in OpenLDAP2 (OpenLDAP 2) 2.2.0 and earlier allows local users to overwrite arbitrary files via a race condition during the creation of a log file for rejected replication requests.

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

It affects 1 product.


Products: Openldap Openldap.

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

Upgrade to a fixed version.

## Is CVE-2002-1508 being exploited?

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

## Other vulnerabilities in Openldap Openldap

- [CVE-2015-3276](https://insights.sbomify.com/CVE-2015-3276/): Weak cryptography in n/a (high 7.5)
- [CVE-2002-1378](https://insights.sbomify.com/CVE-2002-1378/): Memory corruption in n/a (high 7.5)
- [CVE-2002-1379](https://insights.sbomify.com/CVE-2002-1379/): Code injection in n/a (high 7.5)
- [CVE-2002-0045](https://insights.sbomify.com/CVE-2002-0045/): Missing authorization in n/a (high 7.5)
- [CVE-2005-4442](https://insights.sbomify.com/CVE-2005-4442/): Privilege escalation in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1508 is a low-severity vulnerability in Openldap Openldap, published on 11 Feb 2003. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-1508 in the wild and no public exploit code.

Affected product: Openldap Openldap. 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-1508/ (Markdown: https://insights.sbomify.com/CVE-2002-1508/index.md)
```

## Sources

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

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