CVE-2018-6317

CVE-2018-6317 is a critical-severity vulnerability in Claymore Dual Miner Project Claymore Dual Miner with a CVSS 3.x base score of 9.1. Its EPSS exploit-prediction score of 44% places it in the 99th percentile, indicating an elevated likelihood of exploitation. The underlying weakness is classified as CWE-134.

Key facts

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.

Frequently asked questions

What is CVE-2018-6317?
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.
How severe is CVE-2018-6317?
CVE-2018-6317 has a CVSS 3.x base score of 9.1, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability high.
Is CVE-2018-6317 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 44% (99th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2018-6317?
CVE-2018-6317 affects Claymore Dual Miner Project Claymore Dual Miner. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2018-6317?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2018-6317 published?
CVE-2018-6317 was published on 2018-02-02 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Claymore Dual Miner Project Claymore Dual Miner

All CVEs affecting Claymore Dual Miner Project Claymore Dual Miner →

Other CWE-134 vulnerabilities

Browse all CWE-134 vulnerabilities →