# CVE-2002-0512: Privilege escalation in n/a

> Local attackers can escalate privileges by placing malicious libraries in the current working directory when startkde is executed.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** No
- **Published:** 2 Apr 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-49fm-cm32-q45w

## What is CVE-2002-0512?

CVE-2002-0512 is a medium-severity vulnerability in n/a, published on 2 Apr 2003. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

startkde in KDE for Caldera OpenLinux 2.3 through 3.1.1 sets the LD_LIBRARY_PATH environment variable to include the current working directory, which could allow local users to gain privileges of other users running startkde via Trojan horse libraries.

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

It affects 2 products.


Products: Caldera Openlinux Server, Caldera Openlinux Workstation.

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

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

## Is CVE-2002-0512 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2001-1030](https://insights.sbomify.com/CVE-2001-1030/): Auth bypass in n/a (high 7.5)
- [CVE-2001-0980](https://insights.sbomify.com/CVE-2001-0980/): Command injection in n/a (high 7.5)
- [CVE-2002-0004](https://insights.sbomify.com/CVE-2002-0004/): Use after free in n/a (high 7.2)
- [CVE-2002-0835](https://insights.sbomify.com/CVE-2002-0835/): Denial of service in n/a (medium 5.0)
- [CVE-2003-0658](https://insights.sbomify.com/CVE-2003-0658/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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