cve.bz

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

9.8 criticalKEVExploitEPSS 92%Fix available

Known as Silent Bob is Silent

Critical (9.8) in Intel Active Management Technology (AMT), Small Business Technology (SBT), and Standard Manageability. In CISA KEV since 2022-01-28. EPSS 92% estimated probability of exploitation activity in the next 30 days.

On this page
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).

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
92% (unchanged from 92% a week ago; 92% 30 days ago) estimated probability of exploitation activity in the next 30 days; 100th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2022-01-28, due 2022-07-28
CISA's assessment (SSVC)
Exploitation: active · Automatable: yes · Technical impact: total, assessed 2025-02-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-269 Improper Privilege Management
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2017-5689 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2017-5689?via=ask-ai-copy and https://cve.bz/cve/CVE-2017-5689?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2017-5689 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
hpe:proliant_ml10_gen9_server_firmware5.0
siemens:simatic_itp1000_firmwarebefore 9.1.41.3024
siemens:simatic_ipc847d_firmwarebefore 9.1.41.3024
siemens:simatic_ipc847c_firmwarebefore 6.2.61.3535
siemens:simatic_ipc827d_firmwarebefore 9.1.41.3024
siemens:simatic_ipc827c_firmwarebefore 6.2.61.3535
siemens:simatic_ipc677d_firmwarebefore 9.1.41.3024
siemens:simatic_ipc677c_firmwarebefore 6.2.61.3535
siemens:simatic_ipc647d_firmwarebefore 9.1.41.3024
siemens:simatic_ipc647c_firmwarebefore 6.2.61.3535
siemens:simatic_ipc627d_firmwarebefore 9.1.41.3024
siemens:simatic_ipc627c_firmwarebefore 6.2.61.3535
siemens:simatic_ipc547g_firmwarebefore 11.0.26.3000
siemens:simatic_ipc547e_firmwarebefore 9.1.41.3024
siemens:simatic_ipc547d_firmwarebefore 7.1.91.3272
siemens:simatic_ipc477e_firmwarebefore 21.01.05
siemens:simatic_field_pg_m3_firmwarebefore 6.2.61.3535
siemens:simatic_field_pg_m4_firmwarebefore 18.01.06
siemens:simatic_field_pg_m5_firmwarebefore 22.01.03
siemens:simatic_pcs_7_ipc427e_firmwarebefore 21.01.04
siemens:simatic_pcs_7_ipc547d_firmwarebefore 7.1.91.3272
siemens:simatic_pcs_7_ipc547e_firmwarebefore 9.1.41.3024
siemens:simatic_pcs_7_ipc547g_firmwarebefore 11.0.26.3000
siemens:simatic_pcs_7_ipc627c_firmwarebefore 6.2.61.3535
siemens:simatic_pcs_7_ipc677c_firmwarebefore 6.2.61.3535
siemens:simatic_pcs_7_ipc647c_firmwarebefore 6.2.61.3535
siemens:simatic_pcs_7_ipc647d_firmwarebefore 9.1.41.3024
siemens:simatic_pcs_7_ipc847c_firmwarebefore 6.2.61.3535
siemens:simatic_pcs_7_ipc847d_firmwarebefore 9.1.41.3024
siemens:simatic_ipc427e_firmwarebefore 21.01.05
siemens:simotion_p320-4_s_firmwarebefore 17.02.06.83.1
siemens:sinumerik_pcu50.5-p_firmwarebefore 6.2.61.3535
intel:active_management_technology_firmware6.0
intel:active_management_technology_firmware6.1
intel:active_management_technology_firmware6.2
intel:active_management_technology_firmware7.0
intel:active_management_technology_firmware7.1
intel:active_management_technology_firmware8.0
intel:active_management_technology_firmware8.1
intel:active_management_technology_firmware9.0
intel:active_management_technology_firmware9.1
intel:active_management_technology_firmware9.5
intel:active_management_technology_firmware10.0
intel:active_management_technology_firmware11.0
intel:active_management_technology_firmware11.5
intel:active_management_technology_firmware11.6

ICS advisories (CISA)

AdvisoryTitlePublishedSectorsAffectedFixed
ICSA-17-180-01AICSA-17-180-01A_Siemens SIMATIC Industrial PCs, SINUMERIK Panel Control Unit, and SIMOTION P320 (Update A)2017-06-29SINUMERIK Panel Control Unit (PCU): (Intel Core i5 Intel Core i7 and Intel XEON)none listed

From CISA's ICS advisories (CSAF), provided under CISA's notification. Only the facts are shown; each advisory is on CISA's page. Credits.

Public exploits

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

Attack patterns (CAPEC)

  • CAPEC-58 Restful Privilege Elevation Likelihood: High · Severity: High
  • CAPEC-122 Privilege Abuse Likelihood: High · Severity: Medium
  • CAPEC-233 Privilege Escalation

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON