Jiangmin Antivirus 16.0.0.100 Driver KSysCall.sys input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Jiangmin Antivirus 16.0.0.100 and classified as critical. This impacts an unknown function in the library KSysCall.sys of the component Driver. The manipulation leads to input validation. This vulnerability is listed as CVE-2018-6784. The attack must be carried out locally. There is no available exploit.
Details
A vulnerability was found in Jiangmin Antivirus 16.0.0.100 (Anti-Malware Software). It has been rated as problematic. This issue affects an unknown part in the library KSysCall.sys of the component Driver. The manipulation with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
In Jiangmin Antivirus 16.0.0.100, the driver file (KSysCall.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 0x9A00824C.
The bug was discovered 02/06/2018. The weakness was presented 02/06/2018 (Website). The advisory is shared at github.com. The identification of this vulnerability is CVE-2018-6784 since 02/06/2018. An attack has to be approached locally. A simple authentication is necessary for exploitation. 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.
See VDB-112916, VDB-112917, VDB-112914 and VDB-112915 for similar entries. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
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-6784 (🔍)
GCVE (CVE): GCVE-0-2018-6784
GCVE (VulDB): GCVE-100-112913
See also: 🔍
Entry
Created: 02/07/2018 08:22Updated: 01/02/2020 10:39
Changes: 02/07/2018 08:22 (58), 01/02/2020 10:39 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.