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

> Local non-privileged users can crash the system via a NULL pointer dereference in the Kingsoft Internet Security kernel driver.

- **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:** 30 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-68wm-7f94-vq2h

## What is CVE-2018-9151?

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

### Official description

A NULL pointer dereference bug in the function ObReferenceObjectByHandle in the Kingsoft Internet Security 9+ kernel driver KWatch3.sys allows local non-privileged users to crash the system via IOCTL 0x80030030.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Kingsoft Internet Security 9 Plus.

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

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

## Is CVE-2018-9151 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-25949](https://insights.sbomify.com/CVE-2022-25949/): Memory corruption in KINGSOFT Internet Security 9 Plus (high 7.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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