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

> Remote attackers can create directories and overwrite arbitrary files via path traversal in the module parameter, potentially leading to code execution.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/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:** 30 Nov 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-53vr-5mjf-jhrq

## What is CVE-2005-3929?

CVE-2005-3929 is a medium-severity path traversal vulnerability in n/a, published on 30 Nov 2005. It can be exploited over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in the create function in xarMLSXML2PHPBackend.php in Xaraya 1.0 allows remote attackers to create directories and overwrite arbitrary files via ".." sequences in the module parameter to index.php.

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

It affects 1 product.


Products: Xaraya Xaraya.

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

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

## Is CVE-2005-3929 being exploited?

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

Public exploit code:

- Xaraya 1.0.0 RC4 - 'create()' Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-2251](https://insights.sbomify.com/CVE-2007-2251/): Privilege escalation in n/a (high 7.5)
- [CVE-2013-3639](https://insights.sbomify.com/CVE-2013-3639/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-3929 is a medium-severity path traversal vulnerability in n/a, published on 30 Nov 2005. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-3929 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-2005-3929/ (Markdown: https://insights.sbomify.com/CVE-2005-3929/index.md)
```

## Sources

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

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