# CVE-2018-16711: Privilege escalation in n/a

> A local attacker can exploit a kernel driver vulnerability to execute arbitrary code with kernel privileges, leading to full system compromise.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4g9w-hcf4-wx2j

## What is CVE-2018-16711?

CVE-2018-16711 is a high-severity vulnerability in n/a, published on 26 Sep 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IObit Advanced SystemCare, which includes Monitor_win10_x64.sys or Monitor_win7_x64.sys, 1.2.0.5 (and possibly earlier versions) allows a user to send an IOCTL (0x9C402088) with a buffer containing user defined content. The driver's subroutine will execute a wrmsr instruction with the user's buffer for input.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Iobit Advanced Systemcare.

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

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

## Is CVE-2018-16711 being exploited?

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

Public exploit code:

- PoC code for CVE-2018-16711 (exploit by wrmsr) (github_poc): https://github.com/DownWithUp/CVE-2018-16711

## Other vulnerabilities in n/a

- [CVE-2022-24138](https://insights.sbomify.com/CVE-2022-24138/): Privilege escalation in n/a (high 7.8)
- [CVE-2021-44968](https://insights.sbomify.com/CVE-2021-44968/): Use after free in n/a (high 7.8)
- [CVE-2020-14990](https://insights.sbomify.com/CVE-2020-14990/): Path traversal in n/a (high 7.1)
- [CVE-2020-10234](https://insights.sbomify.com/CVE-2020-10234/): Null dereference in n/a (medium 6.5)
- [CVE-2018-16712](https://insights.sbomify.com/CVE-2018-16712/): Information disclosure in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-16711 is a high-severity vulnerability in n/a, published on 26 Sep 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-16711 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-16711/ (Markdown: https://insights.sbomify.com/CVE-2018-16711/index.md)
```

## Sources

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

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