# CVE-2017-16929: Path traversal in n/a

> Authenticated attackers can read or write arbitrary files on Claymore Dual GPU miner systems via directory traversal in the remote management interface.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **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:** 5 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-47pp-3c28-cj5x

## What is CVE-2017-16929?

CVE-2017-16929 is a high-severity path traversal vulnerability in n/a, published on 5 Dec 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The remote management interface on the Claymore Dual GPU miner 10.1 is vulnerable to an authenticated directory traversal vulnerability exploited by issuing a specially crafted request, allowing a remote attacker to read/write arbitrary files. This can be exploited via ../ sequences in the pathname to miner_file or miner_getfile.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2017-16929?

It affects 1 product.


Products: Claymore Dual Miner Project Claymore Dual Miner.

## How do I fix CVE-2017-16929?

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

## Is CVE-2017-16929 being exploited?

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

Public exploit code:

- Claymore Dual ETH + DCR/SC/LBC/PASC GPU Miner - Stack Buffer Overflow / Path Traversal (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2017-16930](https://insights.sbomify.com/CVE-2017-16930/): Memory corruption in n/a (critical 9.8)
- [CVE-2018-6317](https://insights.sbomify.com/CVE-2018-6317/): Information disclosure in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-16929 and fix it if it is affected.

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

## Sources

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

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