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

> Remote attackers can delete arbitrary files or execute code with SYSTEM privileges via directory traversal in Samsung SyncThru.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jun 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-gw89-6xrw-4crf

## What is CVE-2015-5473?

CVE-2015-5473 is a critical path traversal vulnerability in n/a, published on 1 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple directory traversal vulnerabilities in Samsung SyncThru 6 before 1.0 allow remote attackers to delete arbitrary files via unspecified parameters to (1) upload/updateDriver or (2) upload/addDriver or to execute arbitrary code with SYSTEM privileges via unspecified parameters to (3) uploadCloning.html, (4) fileupload.html, (5) uploadFirmware.html, or (6) upload/driver.

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

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

It affects 1 product.


Products: Samsung Syncthru 6.

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

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

## Is CVE-2015-5473 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2015-5473 is a critical path traversal vulnerability in n/a, published on 1 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-5473 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-5473/ (Markdown: https://insights.sbomify.com/CVE-2015-5473/index.md)
```

## Sources

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

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