# CVE-2017-15300: Denial of service in n/a

> An attacker can cause a denial of service in EWBF Cuda Zcash Miner by opening TCP connections to the HTTP API without sending requests, blocking legitimate access to mining statistics.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-q55x-gmhm-qcpf

## What is CVE-2017-15300?

CVE-2017-15300 is a medium-severity denial of service vulnerability in n/a, published on 15 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The miner statistics HTTP API in EWBF Cuda Zcash Miner Version 0.3.4b hangs on incoming TCP connections until some sort of request is made (such as "GET / HTTP/1.1"), which allows for a Denial of Service attack preventing a user from viewing their mining statistics by an attacker opening a session with telnet or netcat and connecting to the miner on the HTTP API port.

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

It affects 1 product.


Products: Ewbf Cuda Zcash Miner.

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

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

## Is CVE-2017-15300 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-15300 is a medium-severity denial of service vulnerability in n/a, published on 15 Oct 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-2017-15300 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-15300/ (Markdown: https://insights.sbomify.com/CVE-2017-15300/index.md)
```

## Sources

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

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