# CVE-2004-2683: Path traversal in n/a

> Attackers can access arbitrary files on InterSystems Cache' servers via the SchemaServer class, leading to information disclosure.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/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:** 20 Aug 2007
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-v78w-74x8-ppvv

## What is CVE-2004-2683?

CVE-2004-2683 is a low-severity path traversal vulnerability in n/a, published on 20 Aug 2007. It can be exploited over the network, with no action from the victim.

### Official description

Unspecified vulnerability in the %XML.Utils.SchemaServer class in InterSystems Cache' 5.0 allows attackers to access arbitrary files on a server.

## Which versions are affected by CVE-2004-2683?

It affects 1 product.


Products: Intersystems Cache.

## How do I fix CVE-2004-2683?

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

## Is CVE-2004-2683 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-17152](https://insights.sbomify.com/CVE-2018-17152/): XML external entity in n/a (medium 6.4)
- [CVE-2018-17150](https://insights.sbomify.com/CVE-2018-17150/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2018-17151](https://insights.sbomify.com/CVE-2018-17151/): Missing authorization in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2683 and fix it if it is affected.

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

## Sources

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

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