Max Secure Anti Virus 19.0.3.019 Driver MaxProtector32.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 Max Secure Anti Virus 19.0.3.019. This impacts an unknown function in the library MaxProtector32.sys of the component Driver. This manipulation causes input validation. The identification of this vulnerability is CVE-2018-6206. The attack can only be executed locally. There is no exploit available.
Details
A vulnerability classified as critical was found in Max Secure Anti Virus 19.0.3.019 (Anti-Malware Software). Affected by this vulnerability is some unknown functionality in the library MaxProtector32.sys of the component Driver. The manipulation with an unknown input leads to a input validation vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
In Max Secure Anti Virus 19.0.3.019,, the driver file (MaxProtector32.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 0x220011.
The bug was discovered 01/24/2018. The weakness was shared 01/25/2018 (Website). The advisory is shared at github.com. This vulnerability is known as CVE-2018-6206 since 01/24/2018. The exploitation appears to be easy. An attack has to be approached locally. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 12/27/2019).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-112431, VDB-112432, VDB-112430 and VDB-112428 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
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: 🔍
0-Day Time: 🔍
Timeline
01/24/2018 🔍01/24/2018 🔍
01/24/2018 🔍
01/25/2018 🔍
01/25/2018 🔍
12/27/2019 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2018-6206 (🔍)
GCVE (CVE): GCVE-0-2018-6206
GCVE (VulDB): GCVE-100-112429
See also: 🔍
Entry
Created: 01/25/2018 14:57Updated: 12/27/2019 15:45
Changes: 01/25/2018 14:57 (59), 12/27/2019 15:45 (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.