EWBF Cuda Zcash Miner 0.3.4b HTTP API TCP Connection data processing
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in EWBF Cuda Zcash Miner 0.3.4b. Affected is an unknown function of the component HTTP API. Performing a manipulation as part of TCP Connection results in data processing. This vulnerability is known as CVE-2017-15300. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability classified as problematic has been found in EWBF Cuda Zcash Miner 0.3.4b. This affects some unknown functionality of the component HTTP API. The manipulation as part of a TCP Connection leads to a data processing vulnerability. CWE is classifying the issue as CWE-19. This is going to have an impact on availability. The summary by CVE is:
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.
The bug was discovered 10/14/2017. The weakness was published 10/15/2017 (Website). The advisory is shared at bitcointalk.org. This vulnerability is uniquely identified as CVE-2017-15300 since 10/14/2017. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Data processingCWE: CWE-19
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
10/14/2017 🔍10/14/2017 🔍
10/15/2017 🔍
10/15/2017 🔍
10/15/2017 🔍
11/24/2019 🔍
Sources
Advisory: bitcointalk.orgStatus: Not defined
CVE: CVE-2017-15300 (🔍)
GCVE (CVE): GCVE-0-2017-15300
GCVE (VulDB): GCVE-100-107865
Entry
Created: 10/15/2017 22:59Updated: 11/24/2019 17:25
Changes: 10/15/2017 22:59 (57), 11/24/2019 17:25 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.