# CVE-2006-4491: Path traversal in n/a

> Authenticated remote attackers can read arbitrary files via directory traversal in Cybozu Collaborex and related products.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jx5q-w98w-3cqr

## What is CVE-2006-4491?

CVE-2006-4491 is a medium-severity path traversal vulnerability in n/a, published on 31 Aug 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in Cybozu Collaborex, AG before 1.2(1.5), AG Pocket before 5.2(0.8), Mailwise before 3.0(0.3), and Garoon 1 before 1.5(4.1) allows remote authenticated users to read arbitrary files via unspecified vectors.

## Which versions are affected by CVE-2006-4491?

It affects 5 products.


Products: Cybozu Collaborex, Cybozu Cybozu Ag, Cybozu Cybozu Pocket, Cybozu Garoon 1, Cybozu Mailwise.

## How do I fix CVE-2006-4491?

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

## Is CVE-2006-4491 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-1334](https://insights.sbomify.com/CVE-2011-1334/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-4491 and fix it if it is affected.

What it is: CVE-2006-4491 is a medium-severity path traversal vulnerability in n/a, published on 31 Aug 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-4491 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-2006-4491/ (Markdown: https://insights.sbomify.com/CVE-2006-4491/index.md)
```

## Sources

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

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