# CVE-2020-7861: AnySupport directory traversing vulnerability

> Attackers can exploit a directory traversal flaw in AnySupport to copy and execute arbitrary files on client PCs.

- **Severity:** High 8.4 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 Apr 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-7xc7-gqfg-jwff

## What is CVE-2020-7861?

CVE-2020-7861 is a high-severity path traversal vulnerability in Koino AquaNPlayer, published on 22 Apr 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

AnySupport (Remote support solution) before 2019.3.21.0 allows directory traversing because of swprintf function to copy file from a management PC to a client PC. This can be lead to arbitrary file execution.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-23 (Relative Path Traversal)

## Which versions are affected by CVE-2020-7861?

It affects 1 product.


Products: Anysupport Anysupport.

## How do I fix CVE-2020-7861?

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

## Is CVE-2020-7861 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-7861 and fix it if it is affected.

What it is: CVE-2020-7861 is a high-severity path traversal vulnerability in Koino AquaNPlayer, published on 22 Apr 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-7861 in the wild and no public exploit code.

Affected product: Koino AquaNPlayer. 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-2020-7861/ (Markdown: https://insights.sbomify.com/CVE-2020-7861/index.md)
```

## Sources

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

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