HWiNFO AMD64 Kernel Driver up to 8.98 memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in HWiNFO AMD64 Kernel Driver up to 8.98. Affected by this vulnerability is an unknown functionality. The manipulation leads to memory corruption. This vulnerability is uniquely identified as CVE-2018-8061. Local access is required to approach this attack. No exploit exists.
Details
A vulnerability was found in HWiNFO AMD64 Kernel Driver up to 8.98 (Hardware Driver Software). It has been rated as critical. This issue affects some unknown processing. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
HWiNFO AMD64 Kernel driver version 8.98 and lower allows an unprivileged user to send IOCTL 0x85FE2608 to the device driver with the HWiNFO32 symbolic device name, resulting in direct physical memory read or write.
The bug was discovered 03/11/2018. The weakness was disclosed 05/10/2018 (Website). The advisory is shared at github.com. The identification of this vulnerability is CVE-2018-8061 since 03/11/2018. The exploitation is known to be easy. An attack has to be approached locally. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 59 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.
The entry VDB-117556 is pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 8.0
- 8.1
- 8.2
- 8.3
- 8.4
- 8.5
- 8.6
- 8.7
- 8.8
- 8.9
- 8.10
- 8.11
- 8.12
- 8.13
- 8.14
- 8.15
- 8.16
- 8.17
- 8.18
- 8.19
- 8.20
- 8.21
- 8.22
- 8.23
- 8.24
- 8.25
- 8.26
- 8.27
- 8.28
- 8.29
- 8.30
- 8.31
- 8.32
- 8.33
- 8.34
- 8.35
- 8.36
- 8.37
- 8.38
- 8.39
- 8.40
- 8.41
- 8.42
- 8.43
- 8.44
- 8.45
- 8.46
- 8.47
- 8.48
- 8.49
- 8.50
- 8.51
- 8.52
- 8.53
- 8.54
- 8.55
- 8.56
- 8.57
- 8.58
- 8.59
- 8.60
- 8.61
- 8.62
- 8.63
- 8.64
- 8.65
- 8.66
- 8.67
- 8.68
- 8.69
- 8.70
- 8.71
- 8.72
- 8.73
- 8.74
- 8.75
- 8.76
- 8.77
- 8.78
- 8.79
- 8.80
- 8.81
- 8.82
- 8.83
- 8.84
- 8.85
- 8.86
- 8.87
- 8.88
- 8.89
- 8.90
- 8.91
- 8.92
- 8.93
- 8.94
- 8.95
- 8.96
- 8.97
- 8.98
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.2VulDB Meta Temp Score: 6.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.1
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: Partially
Local: Yes
Remote: No
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
03/11/2018 🔍03/11/2018 🔍
05/09/2018 🔍
05/10/2018 🔍
05/10/2018 🔍
02/04/2020 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2018-8061 (🔍)
GCVE (CVE): GCVE-0-2018-8061
GCVE (VulDB): GCVE-100-117557
See also: 🔍
Entry
Created: 05/10/2018 11:49Updated: 02/04/2020 08:15
Changes: 05/10/2018 11:49 (57), 02/04/2020 08:15 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.