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

> Remote attackers can access arbitrary files or gain privileges in OSIS LDAP module on Tru64 UNIX via unspecified vectors.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Oct 2007
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-cg5m-v8jp-wc2g

## What is CVE-2002-2265?

CVE-2002-2265 is a medium-severity vulnerability in n/a, published on 18 Oct 2007. It can be exploited over the network, with no action from the victim.

### Official description

Unspecified vulnerability in LDAP Module in System Authentication of Open Source Internet Solutions (OSIS) 5.4 running on Tru64 UNIX 4.0G and 4.0F allows remote attackers to gain access to arbitrary files or gain privileges via unknown attack vectors.

Weakness: CWE-264

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

It affects 1 product.


Products: Open Source Internet Solutions Open Source Internet Solutions.

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

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

## Is CVE-2002-2265 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2002-2265 is a medium-severity vulnerability in n/a, published on 18 Oct 2007. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-2265 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-2265/ (Markdown: https://insights.sbomify.com/CVE-2002-2265/index.md)
```

## Sources

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

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