# CVE-2002-1525: Path traversal in n/a

> Remote attackers can read arbitrary files via directory traversal in the ASTAware SearchDisk engine of Sun ONE Starter Kit.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Mar 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-vqp8-gm28-c2m6

## What is CVE-2002-1525?

CVE-2002-1525 is a medium-severity path traversal vulnerability in n/a, published on 18 Mar 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in ASTAware SearchDisk engine for Sun ONE Starter Kit 2.0 allows remote attackers to read arbitrary files via a .. (dot dot) attack on port (1) 6015 or (2) 6016, or (3) an absolute pathname to port 6017.

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

It affects 2 products.


Products: Astaware Searchdisc, Sun Sunone Starter Kit.

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

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

## Is CVE-2002-1525 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-1525 exists.

Public exploit code:

- Sun ONE Starter Kit 2.0 / ASTAware SearchDisc 3.1 - Search Engine Directory Traversal (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1525 is a medium-severity path traversal vulnerability in n/a, published on 18 Mar 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-1525 exists.

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

## Sources

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

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