K7 Antivirus 15.1.0306 Driver K7Sentry.sys input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in K7 Antivirus 15.1.0306. It has been classified as critical. This vulnerability affects unknown code in the library K7Sentry.sys of the component Driver. The manipulation leads to input validation. This vulnerability is traded as CVE-2018-5220. An attack has to be approached locally. There is no exploit available.
Details
A vulnerability was found in K7 Antivirus 15.1.0306 (Anti-Malware Software) and classified as critical. This issue affects an unknown code block in the library K7Sentry.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 K7 Antivirus 15.1.0306, the driver file (K7Sentry.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 0x95002610.
The bug was discovered 01/04/2018. The weakness was shared 01/04/2018 (Website). The advisory is shared at github.com. The identification of this vulnerability is CVE-2018-5220 since 01/04/2018. An attack has to be approached locally. The requirement for exploitation is a simple 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/19/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-111388, VDB-111386 and VDB-111387 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
License
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/04/2018 🔍01/04/2018 🔍
01/04/2018 🔍
01/04/2018 🔍
01/05/2018 🔍
12/19/2019 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2018-5220 (🔍)
GCVE (CVE): GCVE-0-2018-5220
GCVE (VulDB): GCVE-100-111389
See also: 🔍
Entry
Created: 01/05/2018 08:51Updated: 12/19/2019 19:35
Changes: 01/05/2018 08:51 (59), 12/19/2019 19:35 (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.