# CVE-2019-14612: Memory corruption in Intel(R) NUC(R)

> A privileged local attacker can exploit an out-of-bounds write in Intel NUC firmware to escalate privileges.

- **Severity:** Medium 6.7 (`CVSS:3.1/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:** 16 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-p882-pvrr-mm88

## What is CVE-2019-14612?

CVE-2019-14612 is a medium-severity memory corruption vulnerability in Intel(R) NUC(R), published on 16 Dec 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Out of bounds write in firmware for Intel(R) NUC(R) may allow a privileged user to potentially enable escalation of privilege via local access.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2019-14612?

It affects 19 products.


Products: Intel Cd1iv128mk Firmware, Intel Cd1m3128mk Firmware, Intel Cd1p64gk Firmware, Intel D34010wyb Firmware, Intel De3815tybe Firmware, Intel Nuc6cays Firmware, Intel Nuc6i5syh Firmware, Intel Nuc6i7kyk Firmware, Intel Nuc7cjyh Firmware, Intel Nuc7i3dnhe Firmware, Intel Nuc7i5dnke Firmware, Intel Nuc7i7dnke Firmware, Intel Nuc8i3cysm Firmware, Intel Nuc8i7bek Firmware, Intel Nuc8i7hnk Firmware, Intel Nuc 8 Mainstream Game Kit Firmware, Intel Nuc 8 Mainstream Game Mini Computer Firmware, Intel Stk2m3w64cc Firmware, Intel Stk2mv64cc Firmware.

## How do I fix CVE-2019-14612?

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

## Is CVE-2019-14612 being exploited?

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

## Other vulnerabilities in Intel(R) NUC(R)

- [CVE-2019-14608](https://insights.sbomify.com/CVE-2019-14608/): Privilege escalation in Intel(R) NUC(R) (high 7.8)
- [CVE-2019-14610](https://insights.sbomify.com/CVE-2019-14610/): Privilege escalation in Intel(R) NUC(R) (high 7.8)
- [CVE-2019-14609](https://insights.sbomify.com/CVE-2019-14609/): Privilege escalation in Intel(R) NUC(R) (medium 6.7)
- [CVE-2019-14611](https://insights.sbomify.com/CVE-2019-14611/): Integer overflow in Intel(R) NUC(R) (medium 6.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-14612 and fix it if it is affected.

What it is: CVE-2019-14612 is a medium-severity memory corruption vulnerability in Intel(R) NUC(R), published on 16 Dec 2019. 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-2019-14612 in the wild and no public exploit code.

Affected product: Intel(R) NUC(R). 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-2019-14612/ (Markdown: https://insights.sbomify.com/CVE-2019-14612/index.md)
```

## Sources

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

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