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

> Remote attackers can read arbitrary files and potentially execute code via directory traversal in the url parameter of SAXoPRESS.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9ch4-5494-6263

## What is CVE-2006-1771?

CVE-2006-1771 is a high-severity path traversal vulnerability in n/a, published on 13 Apr 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in misc in pbcs.dll in SAXoTECH SAXoPRESS, aka Saxotech Online (formerly Publicus) allows remote attackers to read arbitrary files and possibly execute arbitrary programs via a .. (dot dot) in the url parameter.

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

It affects 1 product.


Products: Saxotech Saxopress.

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

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

## Is CVE-2006-1771 being exploited?

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

Public exploit code:

- Saxopress - 'URL' Directory Traversal (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-1771 is a high-severity path traversal vulnerability in n/a, published on 13 Apr 2006. 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-2006-1771 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-2006-1771/ (Markdown: https://insights.sbomify.com/CVE-2006-1771/index.md)
```

## Sources

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

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