# CVE-2018-12199: Memory corruption in Intel(R) CSME, Server Platform Services, Trusted Execution Engine and Intel(R) Active Management Technology

> A privileged user with physical access can execute arbitrary code via a buffer overflow in Intel CSME firmware.

- **Severity:** Medium 6.2 (`CVSS:3.0/AV:P/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:** 14 Mar 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-fg3c-2wvr-2695

## What is CVE-2018-12199?

CVE-2018-12199 is a medium-severity memory corruption vulnerability in Intel(R) CSME, Server Platform Services, Trusted Execution Engine and Intel(R) Active Management Technology, published on 14 Mar 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflow in an OS component in Intel CSME before versions 11.8.60, 11.11.60, 11.22.60 or 12.0.20 and Intel TXE version before 3.1.60 or 4.0.10 may allow a privileged user to potentially execute arbitrary code via physical access.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 2 products.


Products: Intel Converged Security Management Engine Firmware, Intel Trusted Execution Engine Firmware.

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

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

## Is CVE-2018-12199 being exploited?

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

## Other vulnerabilities in Intel(R) CSME, Server Platform Services, Trusted Execution Engine and Intel(R) Active Management Technology

- [CVE-2019-0153](https://insights.sbomify.com/CVE-2019-0153/): Memory corruption in Intel(R) Converged Security & Management Engine (CSME) (critical 9.8)
- [CVE-2019-0169](https://insights.sbomify.com/CVE-2019-0169/): Memory corruption in Intel(R) TXE (high 8.8)
- [CVE-2022-36392](https://insights.sbomify.com/CVE-2022-36392/): Denial of service in Intel(R) AMT and Intel(R) Standard Manageability in Intel (R) CSME (high 8.6)
- [CVE-2018-3643](https://insights.sbomify.com/CVE-2018-3643/): Information disclosure in Intel(R) Converged Security and Management Engine (CSME) and Intel(R) Server Platform Services firmware (high 8.2)
- [CVE-2018-3627](https://insights.sbomify.com/CVE-2018-3627/): Privilege escalation in Intel Converged Security Management Engine (Intel CSME) (high 8.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-12199 is a medium-severity memory corruption vulnerability in Intel(R) CSME, Server Platform Services, Trusted Execution Engine and Intel(R) Active Management Technology, published on 14 Mar 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-2018-12199 in the wild and no public exploit code.

Affected product: Intel(R) CSME, Server Platform Services, Trusted Execution Engine and Intel(R) Active Management Technology. 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-12199/ (Markdown: https://insights.sbomify.com/CVE-2018-12199/index.md)
```

## Sources

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

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