# CVE-2002-1379: Code injection in n/a

> Remote or local attackers can execute arbitrary code with elevated privileges via the libldap library when it reads a malicious .ldaprc file.

- **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:** 17 Dec 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-63p4-p8mv-xhx7

## What is CVE-2002-1379?

CVE-2002-1379 is a high-severity code injection vulnerability in Openldap Openldap, published on 17 Dec 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenLDAP2 (OpenLDAP 2) 2.2.0 and earlier allows remote or local attackers to execute arbitrary code when libldap reads the .ldaprc file within applications that are running with extra privileges.

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

It affects 1 product.


Products: Openldap Openldap.

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

Upgrade to a fixed version.

## Is CVE-2002-1379 being exploited?

There is no known exploitation of CVE-2002-1379 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-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)
- [CVE-2007-5707](https://insights.sbomify.com/CVE-2007-5707/): Denial of service in n/a (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1379 is a high-severity code injection vulnerability in Openldap Openldap, published on 17 Dec 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-1379 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-1379/ (Markdown: https://insights.sbomify.com/CVE-2002-1379/index.md)
```

## Sources

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

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