# CVE-2018-12163: Privilege escalation in Intel IoT Developers Kit

> An authenticated local attacker can escalate privileges via DLL injection in the Intel IoT Developers Kit installer.

- **Severity:** Medium 4.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Sep 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-qmp3-m8xr-7xgg

## What is CVE-2018-12163?

CVE-2018-12163 is a medium-severity vulnerability in Intel IoT Developers Kit, published on 12 Sep 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A DLL injection vulnerability in the Intel IoT Developers Kit 4.0 installer may allow an authenticated user to potentially escalate privileges using file modification via local access.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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

It affects 1 product.


Products: Intel Iot Developers Kit.

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

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

## Is CVE-2018-12163 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-12163 is a medium-severity vulnerability in Intel IoT Developers Kit, published on 12 Sep 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-12163 in the wild and no public exploit code.

Affected product: Intel IoT Developers Kit. 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-12163/ (Markdown: https://insights.sbomify.com/CVE-2018-12163/index.md)
```

## Sources

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

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