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

> A local attacker can exploit insufficient input validation in Intel NUC system firmware to elevate privileges to System Management Mode.

- **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 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4fj6-3p83-73vm

## What is CVE-2018-3612?

CVE-2018-3612 is a high-severity vulnerability in n/a, published on 10 May 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Intel NUC kits with insufficient input validation in system firmware, potentially allows a local attacker to elevate privileges to System Management Mode (SMM).

Weakness: CWE-20 (Improper Input Validation)

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

It affects 18 products.


Products: Intel Ayaplcel.86a, Intel Bios, Intel Bnkbl357.86a, Intel Ccsklm30.86a, Intel Ccsklm5v.86a, Intel Dnkbli30.86a, Intel Dnkbli5v.86a, Intel Dnkbli7v.86a, Intel Fybyt10h.86a, Intel Gkaplcpx.86a, Intel Kyskli70.86a, Intel Mkkbli5v.86a, Intel Mkkbly35.86a, Intel Mybdwi30.86a, Intel Mybdwi5v.86a, Intel Rybdwi35.86a, Intel Syskli35.86a, Intel Tybyt10h.86a.

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

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

## Is CVE-2018-3612 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-3612 is a high-severity vulnerability in n/a, published on 10 May 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-3612 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-3612/ (Markdown: https://insights.sbomify.com/CVE-2018-3612/index.md)
```

## Sources

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

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