# CVE-2018-3657: Memory corruption in Intel(R) Active Management Technology

> Privileged local attackers can execute arbitrary code with Intel AMT privileges via buffer overflows in CSME firmware.

- **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:** 12 Sep 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-8rgp-cgf3-c9q6

## What is CVE-2018-3657?

CVE-2018-3657 is a medium-severity memory corruption vulnerability in Intel Active Management Technology Firmware, 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

Multiple buffer overflows in Intel AMT in Intel CSME firmware versions before version 12.0.5 may allow a privileged user to potentially execute arbitrary code with Intel AMT execution privilege via local access.

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

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

It affects 14 products.


Products: Intel Active Management Technology Firmware, Intel Converged Security Management Engine Firmware, Intel Manageability Engine Firmware, Siemens Simatic Field Pg M5 Firmware, Siemens Simatic Ipc427e Firmware, Siemens Simatic Ipc477e Firmware, Siemens Simatic Ipc547e Firmware, Siemens Simatic Ipc627d Firmware, Siemens Simatic Ipc647d Firmware, Siemens Simatic Ipc677d Firmware, Siemens Simatic Ipc827d Firmware, Siemens Simatic Ipc847d Firmware, Siemens Simatic Itp1000 Firmware, Siemens Simatic Pc547g Firmware.

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

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

## Is CVE-2018-3657 being exploited?

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

## Other vulnerabilities in Intel Active Management Technology Firmware

- [CVE-2022-30601](https://insights.sbomify.com/CVE-2022-30601/): Hardcoded credentials in Intel(R) AMT and Intel(R) Standard Manageability (critical 9.8)
- [CVE-2020-8752](https://insights.sbomify.com/CVE-2020-8752/): Memory corruption in Intel(R) AMT, Intel(R) ISM versions (critical 9.8)
- [CVE-2020-8758](https://insights.sbomify.com/CVE-2020-8758/): Memory corruption in Intel(R) AMT and Intel(R) ISM (critical 9.8)
- [CVE-2020-0594](https://insights.sbomify.com/CVE-2020-0594/): Memory corruption in Intel(R) AMT and Intel(R) ISM (critical 9.8)
- [CVE-2020-0595](https://insights.sbomify.com/CVE-2020-0595/): Use after free in Intel(R) AMT and Intel(R) ISM (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-3657 is a medium-severity memory corruption vulnerability in Intel Active Management Technology Firmware, 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-3657 in the wild and no public exploit code.

Affected product: Intel Active Management Technology Firmware. 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-3657/ (Markdown: https://insights.sbomify.com/CVE-2018-3657/index.md)
```

## Sources

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

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