Wibu-Systems WibuKey.sys 6.40 IOCTL Handler Function IRP Request Kernel Memory memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in Wibu-Systems WibuKey.sys 6.40. This issue affects some unknown processing of the component IOCTL Handler Function. Executing a manipulation as part of IRP Request can lead to memory corruption (Kernel Memory). This vulnerability is tracked as CVE-2018-3990. The attack is restricted to local execution. No exploit exists.
Details
A vulnerability was found in Wibu-Systems WibuKey.sys 6.40. It has been declared as critical. This vulnerability affects some unknown functionality of the component IOCTL Handler Function. The manipulation as part of a IRP Request leads to a memory corruption vulnerability (Kernel Memory). The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
An exploitable pool corruption vulnerability exists in the 0x8200E804 IOCTL handler functionality of WIBU-SYSTEMS WibuKey.sys Version 6.40 (Build 2400). A specially crafted IRP request can cause a buffer overflow, resulting in kernel memory corruption and, potentially, privilege escalation. An attacker can send an IRP request to trigger this vulnerability.
The bug was discovered 02/12/2019. The weakness was disclosed 02/05/2019 (Website). The advisory is shared for download at securityfocus.com. This vulnerability was named CVE-2018-3990 since 01/02/2018. The exploitation appears to be easy. The attack needs to be approached locally. No form of authentication is required for a successful exploitation. There are neither technical details nor an exploit publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-130551 and VDB-130553 are pretty similar. VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.5VulDB Meta Temp Score: 7.5
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
CNA Base Score: 9.3
CNA Vector (Talos): 🔍
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
Name: Kernel MemoryClass: Memory corruption / Kernel Memory
CWE: CWE-119
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/02/2018 🔍02/05/2019 🔍
02/06/2019 🔍
02/12/2019 🔍
07/06/2023 🔍
Sources
Advisory: ssa-760124⛔Status: Not defined
Confirmation: 🔍
CVE: CVE-2018-3990 (🔍)
GCVE (CVE): GCVE-0-2018-3990
GCVE (VulDB): GCVE-100-130552
SecurityFocus: 107005
See also: 🔍
Entry
Created: 02/06/2019 13:47Updated: 07/06/2023 09:57
Changes: 02/06/2019 13:47 (56), 05/08/2020 14:09 (3), 07/06/2023 09:56 (4), 07/06/2023 09:57 (12)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.