CVE-2017-5711

Multiple buffer overflows in Active Management Technology (AMT) in Intel Manageability Engine Firmware 8.x/9.x/10.x/11.0/11.5/11.6/11.7/11.10/11.20 allow attacker with local access to the system to execute arbitrary code with AMT execution privilege.

Published: 2017-11-21 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2017-5711 is rated Moderate Risk (46.5/100): CVSS High severity, with low exploitation likelihood (EPSS 0.57%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2017-5711

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.15% 0.57% +0.42%
2 2025-03-30 0.25% 0.15% -0.11%
3 2025-03-29 — 0.25% —

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2017-5711

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]
7.2 2.0 HIGH
AV:L/AC:L/Au:N/C:C/I:C/A:C Click to expand
Access vector (AV:L)
Requires local access to the target system.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:C)
Complete confidentiality impact.
Integrity impact (I:C)
Complete integrity impact.
Availability impact (A:C)
Complete availability impact.
 3.9 10.0 [email protected]

Weakness enumeration for CVE-2017-5711

OS Trackers for CVE-2017-5711

vendor priority summary link
ubuntu medium CVE-2017-5711 medium priority: Ubuntu including 1 source packages (intel-microcode), 5 status rows across 5 suites (artful, trusty, upstream, xenial, zesty): not-affected 4, needs-triage 1. https://ubuntu.com/security/CVE-2017-5711

Affected software / configurations for CVE-2017-5711

Vendor Product Version Raw CPE
intel manageability_engine_firmware >= 8.0.0.0, <= 8.1.71.3608 cpe:2.3:o:intel:manageability_engine_firmware:*:*:*:*:*:*:*:*
intel manageability_engine_firmware >= 9.0.0.0, <= 9.1.41.3024 cpe:2.3:o:intel:manageability_engine_firmware:*:*:*:*:*:*:*:*
intel manageability_engine_firmware >= 10.0.0.0, <= 10.0.55.3000 cpe:2.3:o:intel:manageability_engine_firmware:*:*:*:*:*:*:*:*
intel manageability_engine_firmware 11.0 cpe:2.3:o:intel:manageability_engine_firmware:11.0:*:*:*:*:*:*:*
intel manageability_engine_firmware 11.5 cpe:2.3:o:intel:manageability_engine_firmware:11.5:*:*:*:*:*:*:*
intel manageability_engine_firmware 11.6 cpe:2.3:o:intel:manageability_engine_firmware:11.6:*:*:*:*:*:*:*
intel manageability_engine_firmware 11.7 cpe:2.3:o:intel:manageability_engine_firmware:11.7:*:*:*:*:*:*:*
intel manageability_engine_firmware 11.10 cpe:2.3:o:intel:manageability_engine_firmware:11.10:*:*:*:*:*:*:*
intel manageability_engine_firmware 11.20 cpe:2.3:o:intel:manageability_engine_firmware:11.20:*:*:*:*:*:*:*
intel active_management_technology_firmware — cpe:2.3:o:intel:active_management_technology_firmware:-:*:*:*:*:*:*:*
asus z170-premium_firmware — cpe:2.3:o:asus:z170-premium_firmware:-:*:*:*:*:*:*:*
asus z170-deluxe_firmware — cpe:2.3:o:asus:z170-deluxe_firmware:-:*:*:*:*:*:*:*
asus z170-pro_firmware — cpe:2.3:o:asus:z170-pro_firmware:-:*:*:*:*:*:*:*
asus z170-a_firmware — cpe:2.3:o:asus:z170-a_firmware:-:*:*:*:*:*:*:*
asus z170-ar_firmware — cpe:2.3:o:asus:z170-ar_firmware:-:*:*:*:*:*:*:*
asus z170-e_firmware — cpe:2.3:o:asus:z170-e_firmware:-:*:*:*:*:*:*:*
asus z170-k_firmware — cpe:2.3:o:asus:z170-k_firmware:-:*:*:*:*:*:*:*
asus z170-p_firmware — cpe:2.3:o:asus:z170-p_firmware:-:*:*:*:*:*:*:*
asus z170m-plus_firmware — cpe:2.3:o:asus:z170m-plus_firmware:-:*:*:*:*:*:*:*
asus z170m-plus\/br_firmware — cpe:2.3:o:asus:z170m-plus\/br_firmware:-:*:*:*:*:*:*:*
asus z170-p_d3_firmware — cpe:2.3:o:asus:z170-p_d3_firmware:-:*:*:*:*:*:*:*
asus z170m-e_d3_firmware — cpe:2.3:o:asus:z170m-e_d3_firmware:-:*:*:*:*:*:*:*
asus sabertooth_z170_mark_1_firmware — cpe:2.3:o:asus:sabertooth_z170_mark_1_firmware:-:*:*:*:*:*:*:*
asus sabertooth_z170_s_firmware — cpe:2.3:o:asus:sabertooth_z170_s_firmware:-:*:*:*:*:*:*:*
asus rog_maximus_viii_extreme_firmware — cpe:2.3:o:asus:rog_maximus_viii_extreme_firmware:-:*:*:*:*:*:*:*
asus rog_maximus_viii_ranger_firmware — cpe:2.3:o:asus:rog_maximus_viii_ranger_firmware:-:*:*:*:*:*:*:*
asus rog_maximus_viii_formula_firmware — cpe:2.3:o:asus:rog_maximus_viii_formula_firmware:-:*:*:*:*:*:*:*
asus rog_maximus_viii_hero_firmware — cpe:2.3:o:asus:rog_maximus_viii_hero_firmware:-:*:*:*:*:*:*:*
asus rog_maximus_viii_hero_alpha_firmware — cpe:2.3:o:asus:rog_maximus_viii_hero_alpha_firmware:-:*:*:*:*:*:*:*
asus rog_maximus_viii_gene_firmware — cpe:2.3:o:asus:rog_maximus_viii_gene_firmware:-:*:*:*:*:*:*:*
asus rog_maximus_viii_impact_firmware — cpe:2.3:o:asus:rog_maximus_viii_impact_firmware:-:*:*:*:*:*:*:*
asus z170i_pro_gaming_firmware — cpe:2.3:o:asus:z170i_pro_gaming_firmware:-:*:*:*:*:*:*:*
asus z170_pro_gaming_firmware — cpe:2.3:o:asus:z170_pro_gaming_firmware:-:*:*:*:*:*:*:*
asus z170_pro_gaming\/aura_firmware — cpe:2.3:o:asus:z170_pro_gaming\/aura_firmware:-:*:*:*:*:*:*:*
asus b150_pro_gaming_firmware — cpe:2.3:o:asus:b150_pro_gaming_firmware:-:*:*:*:*:*:*:*
asus b150_pro_gaming\/aura_firmware — cpe:2.3:o:asus:b150_pro_gaming\/aura_firmware:-:*:*:*:*:*:*:*
asus b150i_pro_gaming\/wifi\/aura_firmware — cpe:2.3:o:asus:b150i_pro_gaming\/wifi\/aura_firmware:-:*:*:*:*:*:*:*
asus b150i_pro_gaming\/aura_firmware — cpe:2.3:o:asus:b150i_pro_gaming\/aura_firmware:-:*:*:*:*:*:*:*
asus b150m_pro_gaming_firmware — cpe:2.3:o:asus:b150m_pro_gaming_firmware:-:*:*:*:*:*:*:*
asus b150m-a_firmware — cpe:2.3:o:asus:b150m-a_firmware:-:*:*:*:*:*:*:*
asus b150m-a_d3_firmware — cpe:2.3:o:asus:b150m-a_d3_firmware:-:*:*:*:*:*:*:*
asus b150m-c_d3_firmware — cpe:2.3:o:asus:b150m-c_d3_firmware:-:*:*:*:*:*:*:*
asus b150-a_firmware — cpe:2.3:o:asus:b150-a_firmware:-:*:*:*:*:*:*:*
asus b150m-d_firmware — cpe:2.3:o:asus:b150m-d_firmware:-:*:*:*:*:*:*:*
asus b150m-k_firmware — cpe:2.3:o:asus:b150m-k_firmware:-:*:*:*:*:*:*:*
asus b150m-plus_firmware — cpe:2.3:o:asus:b150m-plus_firmware:-:*:*:*:*:*:*:*
asus b150m-f_plus_firmware — cpe:2.3:o:asus:b150m-f_plus_firmware:-:*:*:*:*:*:*:*
asus b150-plus_firmware — cpe:2.3:o:asus:b150-plus_firmware:-:*:*:*:*:*:*:*
asus b150m-v_plus_firmware — cpe:2.3:o:asus:b150m-v_plus_firmware:-:*:*:*:*:*:*:*
asus ex-b150m-v_firmware — cpe:2.3:o:asus:ex-b150m-v_firmware:-:*:*:*:*:*:*:*
asus ex-b150m-v3_firmware — cpe:2.3:o:asus:ex-b150m-v3_firmware:-:*:*:*:*:*:*:*
asus ex-b150m-v5_firmware — cpe:2.3:o:asus:ex-b150m-v5_firmware:-:*:*:*:*:*:*:*
asus ex-b150-v7_firmware — cpe:2.3:o:asus:ex-b150-v7_firmware:-:*:*:*:*:*:*:*
asus b150-pro_firmware — cpe:2.3:o:asus:b150-pro_firmware:-:*:*:*:*:*:*:*
asus b150m-a\/m.2_firmware — cpe:2.3:o:asus:b150m-a\/m.2_firmware:-:*:*:*:*:*:*:*
asus b150m-c_firmware — cpe:2.3:o:asus:b150m-c_firmware:-:*:*:*:*:*:*:*
asus b150m-c\/br_firmware — cpe:2.3:o:asus:b150m-c\/br_firmware:-:*:*:*:*:*:*:*
asus pio-b150m_firmware — cpe:2.3:o:asus:pio-b150m_firmware:-:*:*:*:*:*:*:*
asus trooper_b150_d3_firmware — cpe:2.3:o:asus:trooper_b150_d3_firmware:-:*:*:*:*:*:*:*
asus b150m-plus_d3_firmware — cpe:2.3:o:asus:b150m-plus_d3_firmware:-:*:*:*:*:*:*:*
asus b150_pro_gaming_d3_firmware — cpe:2.3:o:asus:b150_pro_gaming_d3_firmware:-:*:*:*:*:*:*:*
asus b150m-k_d3_firmware — cpe:2.3:o:asus:b150m-k_d3_firmware:-:*:*:*:*:*:*:*
asus b150-pro_d3_firmware — cpe:2.3:o:asus:b150-pro_d3_firmware:-:*:*:*:*:*:*:*
asus ex-h110m-v_firmware — cpe:2.3:o:asus:ex-h110m-v_firmware:-:*:*:*:*:*:*:*
asus ex-h110m-v3_firmware — cpe:2.3:o:asus:ex-h110m-v3_firmware:-:*:*:*:*:*:*:*
asus h110i-plus_firmware — cpe:2.3:o:asus:h110i-plus_firmware:-:*:*:*:*:*:*:*
asus h110m-a\/dp_firmware — cpe:2.3:o:asus:h110m-a\/dp_firmware:-:*:*:*:*:*:*:*
asus h110m-c_firmware — cpe:2.3:o:asus:h110m-c_firmware:-:*:*:*:*:*:*:*
asus h110m-c\/br_firmware — cpe:2.3:o:asus:h110m-c\/br_firmware:-:*:*:*:*:*:*:*
asus h110m-c\/hdmi_firmware — cpe:2.3:o:asus:h110m-c\/hdmi_firmware:-:*:*:*:*:*:*:*
asus h110m-c\/ps_firmware — cpe:2.3:o:asus:h110m-c\/ps_firmware:-:*:*:*:*:*:*:*
asus h110m-c2_firmware — cpe:2.3:o:asus:h110m-c2_firmware:-:*:*:*:*:*:*:*
asus h110m-c2\/tf_firmware — cpe:2.3:o:asus:h110m-c2\/tf_firmware:-:*:*:*:*:*:*:*
asus h110m-cs_firmware — cpe:2.3:o:asus:h110m-cs_firmware:-:*:*:*:*:*:*:*
asus h110m-cs_x_firmware — cpe:2.3:o:asus:h110m-cs_x_firmware:-:*:*:*:*:*:*:*
asus h110m-cs\/br_firmware — cpe:2.3:o:asus:h110m-cs\/br_firmware:-:*:*:*:*:*:*:*
asus h110m-d\/exper\/si_firmware — cpe:2.3:o:asus:h110m-d\/exper\/si_firmware:-:*:*:*:*:*:*:*
asus h110m-k_x_firmware — cpe:2.3:o:asus:h110m-k_x_firmware:-:*:*:*:*:*:*:*
asus h110m-ks_firmware — cpe:2.3:o:asus:h110m-ks_firmware:-:*:*:*:*:*:*:*
asus h110m-ks_r1_firmware — cpe:2.3:o:asus:h110m-ks_r1_firmware:-:*:*:*:*:*:*:*

References for CVE-2017-5711

cvelogic Threat Intelligence