# CVE-2018-3686: Code injection in INTEL-SA-00086 Detection Tool

> A privileged local user can execute arbitrary code via a code injection flaw in the Intel detection tool.

- **Severity:** Medium 6.7 (`CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **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-hq72-cqgg-mffj

## What is CVE-2018-3686?

CVE-2018-3686 is a medium-severity code injection vulnerability in INTEL-SA-00086 Detection Tool, 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

Code injection vulnerability in INTEL-SA-00086 Detection Tool before version 1.2.7.0 may allow a privileged user to potentially execute arbitrary code via local access.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Intel Sa-00086 Detection Tool.

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

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

## Is CVE-2018-3686 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-3686 is a medium-severity code injection vulnerability in INTEL-SA-00086 Detection Tool, 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-3686 in the wild and no public exploit code.

Affected product: INTEL-SA-00086 Detection Tool. 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-3686/ (Markdown: https://insights.sbomify.com/CVE-2018-3686/index.md)
```

## Sources

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

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