# CVE-2018-3687: Privilege escalation in Intel Quartus II Programmer and Tools

> Local attackers can execute arbitrary code via unquoted service paths in Intel Quartus II Programmer and Tools.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-vx84-2m87-mv3f

## What is CVE-2018-3687?

CVE-2018-3687 is a high-severity vulnerability in Intel Quartus II Programmer and Tools, published on 10 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unquoted service paths in Intel Quartus II Programmer and Tools in versions 11.0 - 15.0 allow a local attacker to potentially execute arbitrary code.

Weakness: CWE-428 (Unquoted Search Path or Element)

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

It affects 1 product.


Products: Intel Quartus Ii Programmer and Tools.

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

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

## Is CVE-2018-3687 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-3687 is a high-severity vulnerability in Intel Quartus II Programmer and Tools, published on 10 Jul 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-3687 in the wild and no public exploit code.

Affected product: Intel Quartus II Programmer and Tools. 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-3687/ (Markdown: https://insights.sbomify.com/CVE-2018-3687/index.md)
```

## Sources

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

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