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

> Remote authenticated attackers can exploit path traversal in Kaseya VSA to write and execute arbitrary files on the server.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 13 Feb 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vwch-7j7j-p95x

## What is CVE-2015-6589?

CVE-2015-6589 is a high-severity path traversal vulnerability in n/a, published on 13 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in Kaseya Virtual System Administrator (VSA) 7.0.0.0 before 7.0.0.33, 8..0.0.0 before 8.0.0.23, 9.0.0.0 before 9.0.0.19, and 9.1.0.0 before 9.1.0.9 allows remote authenticated users to write to and execute arbitrary files due to insufficient restrictions in file paths to json.ashx.

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

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

It affects 1 product.


Products: Kaseya Virtual System Administrator.

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

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

## Is CVE-2015-6589 being exploited?

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

Public exploit code:

- Kaseya Virtual System Administrator (VSA) 7.0 < 9.1 - (Authenticated) Arbitrary File Upload (exploitdb)
- Kaseya Virtual System Administrator (VSA) - Multiple Vulnerabilities (2) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2018-20753](https://insights.sbomify.com/CVE-2018-20753/): Kaseya VSA Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2015-6922](https://insights.sbomify.com/CVE-2015-6922/): Auth bypass in n/a (critical 9.8)
- [CVE-2019-15506](https://insights.sbomify.com/CVE-2019-15506/): Information disclosure in n/a (high 7.5)
- [CVE-2017-12410](https://insights.sbomify.com/CVE-2017-12410/): Race condition in n/a (high 7.4)
- [CVE-2015-2863](https://insights.sbomify.com/CVE-2015-2863/): Open redirect in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-6589 is a high-severity path traversal vulnerability in n/a, published on 13 Feb 2020. Any signed-in user can exploit it 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-2015-6589 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-2015-6589/ (Markdown: https://insights.sbomify.com/CVE-2015-6589/index.md)
```

## Sources

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

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