# CVE-2018-3989: Information disclosure in n/a

> A local attacker can trigger a kernel memory disclosure in the WibuKey driver by sending a crafted IRP request, potentially exposing sensitive kernel data.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Feb 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-r77m-fr9v-2jvr

## What is CVE-2018-3989?

CVE-2018-3989 is a medium-severity vulnerability in n/a, published on 5 Feb 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-908 (Use of Uninitialized Resource)

## Which versions are affected by CVE-2018-3989?

It affects 1 product.


Products: Wibu Wibukey.

## How do I fix CVE-2018-3989?

No fix has been published for CVE-2018-3989 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-3989 being exploited?

There is no known exploitation of CVE-2018-3989 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2018-3990](https://insights.sbomify.com/CVE-2018-3990/): Memory corruption in n/a (critical 9.3)
- [CVE-2024-45181](https://insights.sbomify.com/CVE-2024-45181/): Memory corruption in n/a (high 8.8)
- [CVE-2021-47810](https://insights.sbomify.com/CVE-2021-47810/): WibuKey Runtime 6.51 - 'WkSvW32.exe' Unquoted Service Path (high 8.5)
- [CVE-2024-45182](https://insights.sbomify.com/CVE-2024-45182/): Denial of service in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-3989 and fix it if it is affected.

What it is: CVE-2018-3989 is a medium-severity vulnerability in n/a, published on 5 Feb 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-3989 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-3989/ (Markdown: https://insights.sbomify.com/CVE-2018-3989/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-3989
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-3989
- OSV: https://osv.dev/vulnerability/CVE-2018-3989

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-3989/
Summaries are generated and may contain mistakes; the official description above is the record.