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

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

• Documented patch — www.oracle.com (NIST National Vulnerability Database)
• Documented patch — security-center.intel.com (NIST National Vulnerability Database)

CISA required action CISA

Apply updates per vendor instructions.

US federal deadline: Jul 28, 2022 — passed 1540 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

1. Identify exposed assets running the affected vendor/product/version combinations (Hpe Proliant Ml10 Gen9 Server Firmware, Intel Active Management Technology Firmware, Intel Intel Active Mangement Technology, Intel Small Business Technology, Intel Standard Manageability…).
2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
3. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
4. Apply the fixed version or the patch documented under Remediation.
5. EPSS ahead of 100% of scored CVEs: prioritize it in the patch queue.
6. Search available logs for exploit probes matching the vulnerability class (privilege escalation), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-269 · Improper Privilege Management

Other CVEs with this weakness →

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

Public exploits, PoCs and detection templates

Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.

Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 92.19%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

• Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
• Hunt retroactively in logs from before Jan 28, 2022 (KEV listing): exploitation may have started earlier.

Timeline

What happened to this CVE, newest first.

• 2026
• Affected products added · intel corporation/intel active mangement technology, intel small business technology, intel standard manageability
  Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
• SSVC assessment updated
  Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
• Record published
  Oct 13, 2026
• Fix documented
  Oct 13, 2026 · NIST National Vulnerability Database
• Affected products added · hpe/proliant ml10 gen9 server firmware, siemens/simatic itp1000 firmware, siemens/simatic ipc847d firmware, siemens/sima
  Oct 13, 2026 · NIST National Vulnerability Database
• CVSS changed · 9.8
  Oct 13, 2026 · NIST National Vulnerability Database
• Source status changed · → Analyzed
  Oct 13, 2026 · NIST National Vulnerability Database
• Added to CISA KEV (detected)
  Oct 13, 2026 · CISA Known Exploited Vulnerabilities
• Record created in this database
  Oct 13, 2026 · CISA Known Exploited Vulnerabilities
• 2022
• Added to CISA KEV catalog
  Jan 27, 2022 · CISA
• 2017
• CVE published
  May 2, 2017 · intel

Source activity

Repeated readings are counted rather than listed.

• 2× References added · Oct 13, 2026 – Oct 13, 2026
• 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

15 on the record

• www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html
  Patch, Third Party Advisory, x_refsource_CONFIRM, NIST National Vulnerability Database
• security-center.intel.com/advisory.aspx
  Patch, Vendor Advisory, x_refsource_CONFIRM, NIST National Vulnerability Database
• www.cisa.gov/known-exploited-vulnerabilities-catalog
  US Government Resource, NIST National Vulnerability Database
• security.netapp.com/advisory/ntap-20170509-0001
  GitHub Security Advisories
• www.securitytracker.com/id/1038385
  Broken Link, Third Party Advisory, VDB Entry, vdb-entry, x_refsource_SECTRACK, NIST National Vulnerability Database
• www.securityfocus.com/bid/98269
  Broken Link, Third Party Advisory, VDB Entry, vdb-entry, x_refsource_BID, NIST National Vulnerability Database
• www.embedi.com/files/white-papers/Silent-Bob-is-Silent.pdf
  Broken Link, Exploit, Technical Description, Third Party Advisory, x_refsource_MISC, NIST National Vulnerability Database
• www.tenable.com/blog/rediscovering-the-intel-amt-vulnerability
  Technical Description, Third Party Advisory, x_refsource_MISC, NIST National Vulnerability Database
• cert-portal.siemens.com/productcert/pdf/ssa-874235.pdf
  Third Party Advisory, x_refsource_CONFIRM, NIST National Vulnerability Database
• h20566.www2.hpe.com/hpsc/doc/public/display
  Third Party Advisory, x_refsource_CONFIRM, NIST National Vulnerability Database
• nvd.nist.gov/vuln/detail/CVE-2017-5689
  GitHub Security Advisories
• www.embedi.com/news/mythbusters-cve-2017-5689
  Broken Link, Third Party Advisory, x_refsource_MISC, NIST National Vulnerability Database
• downloadmirror.intel.com/26754/eng/INTEL-SA-00075%20Mitigation%20Guide-Rev%201.1.pdf
  Broken Link, x_refsource_CONFIRM, NIST National Vulnerability Database
• github.com/advisories/GHSA-v6j9-wwcx-4984
  GitHub Security Advisories
• security.netapp.com/advisory/ntap-20170509-0001/
  Third Party Advisory, x_refsource_CONFIRM, NIST National Vulnerability Database

Elsewhere on this site

Related CVEs (same products)

• Medium CVE-2020-8670 Race condition in the firmware for some Intel(R) Processors may allow a privileged user to... Jun 9, 2021
• Medium CVE-2020-12357 Improper initialization in the firmware for some Intel(R) Processors may allow a privileged user... Jun 9, 2021
• Medium CVE-2020-12358 Out of bounds write in the firmware for some Intel(R) Processors may allow a privileged user to... Jun 9, 2021
• High CVE-2020-12360 Out-of-bounds Read in Intel Bios Jun 9, 2021
• Medium CVE-2020-24486 Improper Input Validation in Intel Bios Jun 9, 2021

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

• No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
• No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
• No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2017-5689 is "Intel Active Management Technology (AMT), Small Business Technology (SBT), and Standard Manageability Privilege Escalation Vulnerability", rated Critical. It affects Proliant Ml10 Gen9 Server Firmware (Hpe); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 9.8 describes technical severity. EPSS 92.19% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.