Advanced SystemCare Ultimate 11.0.1.58 Driver Monitor_win7_x64.sys input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Advanced SystemCare Ultimate 11.0.1.58. Affected by this vulnerability is an unknown functionality in the library Monitor_win7_x64.sys of the component Driver. Performing a manipulation results in input validation. This vulnerability is known as CVE-2018-9002. Attacking locally is a requirement. No exploit is available.
Details
A vulnerability, which was classified as critical, was found in Advanced SystemCare Ultimate 11.0.1.58. This affects some unknown functionality in the library Monitor_win7_x64.sys of the component Driver. The manipulation with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
In Advanced SystemCare Ultimate 11.0.1.58, the driver file (Monitor_win7_x64.sys) allows local users to cause a denial of service (BSOD) or possibly have unspecified other impact because of not validating input values from IOCtl 0x9c4060cc.
The bug was discovered 03/26/2018. The weakness was published 03/25/2018 (Website). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2018-9002 since 03/24/2018. An attack has to be approached locally. A authentication is required for exploitation. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Similar entries are available at VDB-115009, VDB-115008, VDB-115006 and VDB-115007. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.2VulDB Meta Temp Score: 7.2
VulDB Base Score: 6.6
VulDB Temp Score: 6.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
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: Input validationCWE: CWE-20
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: 🔍
Timeline
03/24/2018 🔍03/24/2018 🔍
03/25/2018 🔍
03/25/2018 🔍
03/26/2018 🔍
01/16/2020 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2018-9002 (🔍)
GCVE (CVE): GCVE-0-2018-9002
GCVE (VulDB): GCVE-100-115005
See also: 🔍
Entry
Created: 03/25/2018 10:09Updated: 01/16/2020 15:22
Changes: 03/25/2018 10:09 (56), 01/16/2020 15:22 (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.