I-O DATA DEVICE LAN DISK Connect up to 2.02 memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in I-O DATA DEVICE LAN DISK Connect up to 2.02. This issue affects some unknown processing. Performing a manipulation results in memory corruption. This vulnerability is identified as CVE-2017-10875. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability was found in I-O DATA DEVICE LAN DISK Connect up to 2.02. It has been classified as problematic. This affects some unknown processing. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on availability. The summary by CVE is:
I-O DATA DEVICE LAN DISK Connect Ver2.02 and earlier allows an attacker to cause a denial of service in the application via unspecified vectors.
The bug was discovered 11/06/2017. The weakness was released 11/13/2017 (Website). It is possible to read the advisory at jvn.jp. This vulnerability is uniquely identified as CVE-2017-10875 since 07/04/2017. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 7 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.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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: Memory corruptionCWE: CWE-119
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
07/04/2017 🔍11/06/2017 🔍
11/13/2017 🔍
11/13/2017 🔍
11/14/2017 🔍
12/05/2019 🔍
Sources
Advisory: jvn.jpStatus: Not defined
Confirmation: 🔍
CVE: CVE-2017-10875 (🔍)
GCVE (CVE): GCVE-0-2017-10875
GCVE (VulDB): GCVE-100-109311
Entry
Created: 11/14/2017 14:14Updated: 12/05/2019 17:45
Changes: 11/14/2017 14:14 (56), 12/05/2019 17:45 (1)
Complete: 🔍
Cache ID: 216:4AC:103
No comments yet. Languages: en.
Please log in to comment.