# CVE-2005-2891: Path traversal in n/a

> Remote attackers can read or write arbitrary files via unsafe ActiveX methods, requiring user interaction to trigger the vulnerability.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Sep 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9v5h-pjw2-wf2g

## What is CVE-2005-2891?

CVE-2005-2891 is a medium-severity path traversal vulnerability in n/a, published on 14 Sep 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

WebArchiveX.dll 5.5.0.76 installed before September 6th, 2005 is marked safe for scripting by default, which allows remote attackers to read or write to arbitrary files via the (1) MakeArchive or (2) MakeArchiveStr methods.

## Which versions are affected by CVE-2005-2891?

It affects 1 product.


Products: Csystems Webarchivex.

## How do I fix CVE-2005-2891?

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

## Is CVE-2005-2891 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2891 and fix it if it is affected.

What it is: CVE-2005-2891 is a medium-severity path traversal vulnerability in n/a, published on 14 Sep 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2005-2891 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-2005-2891/ (Markdown: https://insights.sbomify.com/CVE-2005-2891/index.md)
```

## Sources

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

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