Jiangmin Antivirus 16.0.0.100 Driver KVFG.sys input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Jiangmin Antivirus 16.0.0.100. It has been rated as critical. This affects an unknown part in the library KVFG.sys of the component Driver. Performing a manipulation results in input validation. This vulnerability is reported as CVE-2018-6788. The attack requires a local approach. No exploit exists.
Details
A vulnerability, which was classified as problematic, was found in Jiangmin Antivirus 16.0.0.100 (Anti-Malware Software). This affects an unknown function in the library KVFG.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 Jiangmin Antivirus 16.0.0.100, the driver file (KVFG.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 0x2208C0.
The bug was discovered 02/06/2018. The weakness was disclosed 02/06/2018 (Website). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2018-6788 since 02/06/2018. An attack has to be approached locally. The successful exploitation requires a 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 01/02/2020).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-112916, VDB-112914, VDB-112915 and VDB-112913 are 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
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.5
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
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
02/06/2018 🔍02/06/2018 🔍
02/06/2018 🔍
02/06/2018 🔍
02/07/2018 🔍
01/02/2020 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2018-6788 (🔍)
GCVE (CVE): GCVE-0-2018-6788
GCVE (VulDB): GCVE-100-112917
See also: 🔍
Entry
Created: 02/07/2018 08:22Updated: 01/02/2020 11:02
Changes: 02/07/2018 08:22 (58), 01/02/2020 11:02 (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.