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

> Remote attackers can read arbitrary files in Interchange when running in INET mode, exposing sensitive data.

- **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:** Yes
- **Published:** 20 Aug 2002
- **Updated:** 8 Aug 2024
- **Also known as:** DSA-150, GHSA-353w-p8pv-g278

## What is CVE-2002-0874?

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

### Official description

Vulnerability in Interchange 4.8.6, 4.8.3, and other versions, when running in INET mode, allows remote attackers to read arbitrary files.

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

It affects 1 product.


Products: Redhat Interchange.

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

Apply the vendor's patch.

## Is CVE-2002-0874 being exploited?

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

Public exploit code:

- RedHat Interchange 4.8.x - Arbitrary File Read (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2020-12685](https://insights.sbomify.com/CVE-2020-12685/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2003-1138](https://insights.sbomify.com/CVE-2003-1138/): The default configuration of Apache 2.0.40, as shipped with Red Hat Linux 9.0, allows remote attackers to list directory contents, even if a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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