# CVE-2018-8060: Null dereference in n/a

> An unprivileged user can trigger a Windows kernel panic via a null pointer dereference in the HWiNFO AMD64 kernel driver, causing a system crash.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-f5hv-4vv9-w36h

## What is CVE-2018-8060?

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

### Official description

HWiNFO AMD64 Kernel driver version 8.98 and lower allows an unprivileged user to send an IOCTL to the device driver. If input and/or output buffer pointers are NULL or if these buffers' data are invalid, a NULL/invalid pointer access occurs, resulting in a Windows kernel panic aka Blue Screen. This affects IOCTLs higher than 0x85FE2600 with the HWiNFO32 symbolic device name.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Hwinfo Amd64 Kernel Driver.

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

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

## Is CVE-2018-8060 being exploited?

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

Public exploit code:

- Simple IOCTL dispatcher for CVE-2018-8060/8061 (github_poc): https://github.com/otavioarj/SIOCtl

## Other vulnerabilities in n/a

- [CVE-2018-8061](https://insights.sbomify.com/CVE-2018-8061/): Privilege escalation in n/a (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-8060 is a medium-severity vulnerability in n/a, published on 10 May 2018. 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-8060 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-8060/ (Markdown: https://insights.sbomify.com/CVE-2018-8060/index.md)
```

## Sources

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

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