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

> Remote attackers can determine the existence of arbitrary directories via path traversal in the album parameter, leading to information disclosure.

- **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:** 28 Jun 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-4qf2-7vj7-p7mr

## What is CVE-2002-1837?

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

### Official description

The getAlbumToDisplay function in idsShared.pm for Image Display System (IDS) 0.81 allows remote attackers to determine the existence of arbitrary directories via ".." sequences in the album parameter, which generates different error messages depending on whether the directory exists or not.

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

It affects 1 product.


Products: Ids Ids.

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

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

## Is CVE-2002-1837 being exploited?

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

Public exploit code:

- Image Display System 0.8.1 - Directory Existence Disclosure (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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