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

> Remote attackers can read arbitrary files on SunPS iRunbook servers by exploiting a path traversal vulnerability in none.php.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-v522-77pj-3mfp

## What is CVE-2002-1034?

CVE-2002-1034 is a critical path traversal vulnerability in n/a, published on 31 Aug 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

none.php for SunPS iRunbook 2.5.2 allows remote attackers to read arbitrary files via an absolute pathname in the argument.

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

It affects 1 product.


Products: Sun I-Runbook.

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

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

## Is CVE-2002-1034 being exploited?

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

Public exploit code:

- Sun i-Runbook 2.5.2 - Directory and File Content Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2002-1033](https://insights.sbomify.com/CVE-2002-1033/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1034 is a critical path traversal vulnerability in n/a, published on 31 Aug 2002. 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-1034 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-1034/ (Markdown: https://insights.sbomify.com/CVE-2002-1034/index.md)
```

## Sources

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

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