# CVE-2015-8357: Path traversal in n/a

> Authenticated attackers can exploit a directory traversal flaw in the Bitrix xscan module to rename arbitrary files, leading to information disclosure or denial of service.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **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:** 16 Dec 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-ghq7-vvp6-23x7

## What is CVE-2015-8357?

CVE-2015-8357 is a medium-severity path traversal vulnerability in n/a, published on 16 Dec 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in the bitrix.xscan module before 1.0.4 for Bitrix allows remote authenticated users to rename arbitrary files, and consequently obtain sensitive information or cause a denial of service, via a .. (dot dot) in the file parameter to admin/bitrix.xscan_worker.php.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2015-8357?

It affects 1 product.


Products: Bitrix Xscan.

## How do I fix CVE-2015-8357?

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

## Is CVE-2015-8357 being exploited?

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

Public exploit code:

- Bitrix bitrix.xscan Module 1.0.3 - Directory Traversal (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-8357 and fix it if it is affected.

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

## Sources

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

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