# CVE-2018-6317: Information disclosure in n/a

> Remote attackers can exploit a format string vulnerability in Claymore Dual Miner to read memory or cause denial of service.

- **Severity:** Critical 9.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 2 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-x6jm-rxp5-jx5q

## What is CVE-2018-6317?

CVE-2018-6317 is a critical vulnerability in n/a, published on 2 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The remote management interface in Claymore Dual Miner 10.5 and earlier is vulnerable to an unauthenticated format string vulnerability, allowing remote attackers to read memory or cause a denial of service.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

## Which versions are affected by CVE-2018-6317?

It affects 1 product.


Products: Claymore Dual Miner Project Claymore Dual Miner.

## How do I fix CVE-2018-6317?

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

## Is CVE-2018-6317 being exploited?

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

Public exploit code:

- Claymore Dual GPU Miner 10.5 - Format String (exploitdb)
- Claymore Dual GPU Miner  Format String dos attack (metasploit)

## Other vulnerabilities in n/a

- [CVE-2017-16930](https://insights.sbomify.com/CVE-2017-16930/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-16929](https://insights.sbomify.com/CVE-2017-16929/): Path traversal in n/a (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-6317 and fix it if it is affected.

What it is: CVE-2018-6317 is a critical vulnerability in n/a, published on 2 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-6317 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-2018-6317/ (Markdown: https://insights.sbomify.com/CVE-2018-6317/index.md)
```

## Sources

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

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