{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-6317 exists.","fix":"No fix has been published for CVE-2018-6317 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2018-6317 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-6317 exists.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2018-6317/ (Markdown: https://insights.sbomify.com/CVE-2018-6317/index.md)","id":"CVE-2018-6317","markdown":"https://insights.sbomify.com/CVE-2018-6317/index.md","name":"CVE-2018-6317","record":{"aliases":["GHSA-x6jm-rxp5-jx5q"],"analysis":{"component_type":"other","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"cryptocurrency mining software","requires_auth":"none","summary":"Remote attackers can exploit a format string vulnerability in Claymore Dual Miner to read memory or cause denial of service.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"claymore_dual_miner","vendor":"claymore_dual_miner_project"}],"cvss":{"score":9.1,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-134","name":"Use of Externally-Controlled Format String"}],"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.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2018-02-05","github_poc":0,"max_poc_stars":null,"metasploit":1,"nuclei":0,"refs":[{"date":"2018-02-05","kind":"exploitdb","ref":"43972","stars":null,"title":"Claymore Dual GPU Miner 10.5 - Format String"},{"date":"2018-02-06","kind":"metasploit","ref":"auxiliary/dos/tcp/claymore_dos","stars":null,"title":"Claymore Dual GPU Miner  Format String dos attack"}],"tier":"weaponised"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2018-6317","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Other in n/a","id":"CVE-2018-6318"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2018-6316"},"products":["n/a"],"published":"2018-02-02","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2017-16930","kev_date_added":null,"published":"2017-12-05"},{"cvss_score":8.1,"headline":"Path traversal in n/a","id":"CVE-2017-16929","kev_date_added":null,"published":"2017-12-05"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Remote attackers can exploit a format string vulnerability in Claymore Dual Miner to read memory or cause denial of service.","url":"https://insights.sbomify.com/CVE-2018-6317/"}