Ikarus anti.virus up to 2.16.17 Driver ntguard.sys input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Ikarus anti.virus up to 2.16.17. It has been classified as critical. Impacted is an unknown function in the library ntguard.sys of the component Driver. The manipulation leads to input validation. This vulnerability is referenced as CVE-2017-14965. The attack can only be performed from a local environment. No exploit is available. Upgrading the affected component is recommended.
Details
A vulnerability was found in Ikarus anti.virus up to 2.16.17 (Anti-Malware Software) and classified as critical. This issue affects an unknown code block in the library ntguard.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 IKARUS anti.virus before 2.16.18, the ntguard.sys driver contains an Arbitrary Write vulnerability because of not validating input values from IOCtl 0x830000cc.
The bug was discovered 12/20/2017. The weakness was published 12/20/2017 (Website). The advisory is shared at greyhathacker.net. The identification of this vulnerability is CVE-2017-14965 since 10/01/2017. The exploitation is known to be easy. An attack has to be approached locally. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.
Upgrading to version 2.16.18 eliminates this vulnerability.
Similar entries are available at VDB-110882, VDB-110883, VDB-110884 and VDB-110886. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 2.16.0
- 2.16.1
- 2.16.2
- 2.16.3
- 2.16.4
- 2.16.5
- 2.16.6
- 2.16.7
- 2.16.8
- 2.16.9
- 2.16.10
- 2.16.11
- 2.16.12
- 2.16.13
- 2.16.14
- 2.16.15
- 2.16.16
- 2.16.17
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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 |
OpenVAS ID: 63443
OpenVAS Name: IKARUS anti.virus Multiple Arbitrary/Out of Bounds Write Vulnerabilities
OpenVAS File: 🔍
OpenVAS Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: anti.virus 2.16.18
Timeline
10/01/2017 🔍12/20/2017 🔍
12/20/2017 🔍
12/20/2017 🔍
12/21/2017 🔍
12/16/2019 🔍
Sources
Advisory: greyhathacker.netStatus: Not defined
CVE: CVE-2017-14965 (🔍)
GCVE (CVE): GCVE-0-2017-14965
GCVE (VulDB): GCVE-100-110885
See also: 🔍
Entry
Created: 12/21/2017 08:35Updated: 12/16/2019 16:40
Changes: 12/21/2017 08:35 (64), 12/16/2019 16:40 (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.