# CVE-2017-5689: Intel Active Management Technology (AMT), Small Business Technology (SBT), and Standard Manageability Privilege Escalation

> Unprivileged attackers can bypass authentication to gain system privileges on Intel manageability firmware, requiring immediate patching.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 28 Jan 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 May 2017
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-v6j9-wwcx-4984

## What is CVE-2017-5689?

CVE-2017-5689 is a critical authentication bypass vulnerability in Intel Active Management Technology Firmware, published on 2 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unprivileged network attacker could gain system privileges to provisioned Intel manageability SKUs: Intel Active Management Technology (AMT) and Intel Standard Manageability (ISM). An unprivileged local attacker could provision manageability features gaining unprivileged network or local system privileges on Intel manageability SKUs: Intel Active Management Technology (AMT), Intel Standard Manageability (ISM), and Intel Small Business Technology (SBT).

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2017-5689?

It affects 36 products.


Products: Hpe Proliant Ml10 Gen9 Server Firmware, Intel Active Management Technology Firmware, Siemens Simatic Field Pg M3 Firmware, Siemens Simatic Field Pg M4 Firmware, Siemens Simatic Field Pg M5 Firmware, Siemens Simatic Ipc427d Firmware, Siemens Simatic Ipc427e Firmware, Siemens Simatic Ipc477d Firmware, Siemens Simatic Ipc477e Firmware, Siemens Simatic Ipc547d Firmware, Siemens Simatic Ipc547e Firmware, Siemens Simatic Ipc547g Firmware, Siemens Simatic Ipc627c Firmware, Siemens Simatic Ipc627d Firmware, Siemens Simatic Ipc647c Firmware, Siemens Simatic Ipc647d Firmware, Siemens Simatic Ipc677c Firmware, Siemens Simatic Ipc677d Firmware, Siemens Simatic Ipc827c Firmware, Siemens Simatic Ipc827d Firmware and 16 more.

## How do I fix CVE-2017-5689?

No fix has been published for CVE-2017-5689 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 28 Jul 2022.

## Is CVE-2017-5689 being exploited?

Yes. Attackers have exploited CVE-2017-5689 in the wild since at least 28 Jan 2022.

Public exploit code:

- CVE-2017-5689 Proof-of-Concept exploit (github_poc): https://github.com/embedi/amt_auth_bypass_poc
- https://github.com/CerberusSecurity/CVE-2017-5689 (github_poc): https://github.com/CerberusSecurity/CVE-2017-5689
- simple python poc for CVE-2017-5689 (github_poc): https://github.com/Bijaye/intel_amt_bypass
- Honeypot for Intel's AMT Firmware Vulnerability CVE-2017-5689 (github_poc): https://github.com/MlSebrell/amthoneypot
- Intel AMT Digest Authentication Bypass Scanner (metasploit)
- Intel Active Management Technology - System Privileges (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-5689 and fix it if it is affected.

What it is: CVE-2017-5689 is a critical authentication bypass vulnerability in Intel Active Management Technology Firmware, published on 2 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2017-5689 in the wild since at least 28 Jan 2022.

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-2017-5689/ (Markdown: https://insights.sbomify.com/CVE-2017-5689/index.md)
```

## Sources

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

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