# CVE-2018-12160: Privilege escalation in Intel(R) Data Migration Software

> An authenticated local attacker can execute arbitrary code via DLL injection due to insecure default directory permissions in the Intel Data Center Migration Center installer.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 12 Sep 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-wgg2-9vvc-4wxr

## What is CVE-2018-12160?

CVE-2018-12160 is a medium-severity vulnerability in Intel(R) Data Migration Software, published on 12 Sep 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

DLL injection vulnerability in software installer for Intel Data Center Migration Center Software v3.1 and before may allow an authenticated user to potentially execute code using default directory permissions via local access.

Weakness: CWE-427 (Uncontrolled Search Path Element), CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Intel Data Migration Software.

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

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

## Is CVE-2018-12160 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-12160 is a medium-severity vulnerability in Intel(R) Data Migration Software, published on 12 Sep 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-12160 in the wild and no public exploit code.

Affected product: Intel(R) Data Migration Software. 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-12160/ (Markdown: https://insights.sbomify.com/CVE-2018-12160/index.md)
```

## Sources

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

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