Wibu-Systems WibuKey.sys 6.40 IOCTL Handler Function IRP Request information disclosure
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
4.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Wibu-Systems WibuKey.sys 6.40. It has been declared as problematic. This vulnerability affects unknown code of the component IOCTL Handler Function. The manipulation as part of IRP Request leads to information disclosure. This vulnerability was named CVE-2018-3989. Local access is required to approach this attack. There is no exploit available. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Details
A vulnerability was found in Wibu-Systems WibuKey.sys 6.40. It has been classified as problematic. This affects an unknown functionality of the component IOCTL Handler Function. The manipulation as part of a IRP Request leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. The summary by CVE is:
An exploitable kernel memory disclosure 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 the driver to return uninitialized memory, resulting in kernel memory disclosure. An attacker can send an IRP request to trigger this vulnerability.
The bug was discovered 02/12/2019. The weakness was released 02/05/2019 (Website). It is possible to read the advisory at securityfocus.com. This vulnerability is uniquely identified as CVE-2018-3989 since 01/02/2018. The exploitability is told to be easy. Attacking locally is a requirement. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Entries connected to this vulnerability are available at VDB-130552 and VDB-130553. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.4
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
CNA Base Score: 4.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
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
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-3989 (🔍)
GCVE (CVE): GCVE-0-2018-3989
GCVE (VulDB): GCVE-100-130551
SecurityFocus: 107005
See also: 🔍
Entry
Created: 02/06/2019 13:46Updated: 07/06/2023 09:55
Changes: 02/06/2019 13:46 (56), 05/08/2020 14:05 (3), 07/06/2023 09:53 (4), 07/06/2023 09:55 (10)
Complete: 🔍
Cache ID: 216:965:103
No comments yet. Languages: en.
Please log in to comment.