7.2
HIGH
CVE-2017-5712
Intel AMT Buffer Overflow Vulnerability
Description
Buffer overflow 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 allows attacker with remote Admin access to the system to execute arbitrary code with AMT execution privilege.
INFO
Published Date :
Nov. 21, 2017, 2:29 p.m.
Last Modified :
May 22, 2023, 4:18 p.m.
Source :
[email protected]
Remotely Exploitable :
Yes !
Impact Score :
5.9
Exploitability Score :
1.2
Public PoC/Exploit Available at Github
CVE-2017-5712 has a 1 public PoC/Exploit available at Github.
Go to the Public Exploits tab to see the list.
Affected Products
The following products are affected by CVE-2017-5712
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2017-5712.
| URL | Resource |
|---|---|
| http://www.securityfocus.com/bid/101920 | Third Party Advisory VDB Entry |
| http://www.securitytracker.com/id/1039852 | Issue Tracking Third Party Advisory VDB Entry |
| https://cert-portal.siemens.com/productcert/pdf/ssa-892715.pdf | Third Party Advisory |
| https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00086&languageid=en-fr | Issue Tracking Vendor Advisory |
| https://security.netapp.com/advisory/ntap-20171120-0001/ | Issue Tracking Third Party Advisory |
| https://www.asus.com/News/wzeltG5CjYaIwGJ0 | Third Party Advisory |
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Ansible play to check if remote host is vulnearable to Intel-SA-00086
Updated: 6 years, 11 months ago
2 stars
0 fork
0 watcher
Born at : Nov. 24, 2017, 9:39 a.m.
This repo has been linked 8 different CVEs too.
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2017-5712 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2017-5712 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
Modified Analysis by [email protected]
May. 22, 2023
Action Type Old Value New Value Removed CVSS V3 NIST AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H Added CVSS V3.1 NIST AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H Changed Reference Type https://cert-portal.siemens.com/productcert/pdf/ssa-892715.pdf No Types Assigned https://cert-portal.siemens.com/productcert/pdf/ssa-892715.pdf Third Party Advisory Changed Reference Type https://www.asus.com/News/wzeltG5CjYaIwGJ0 No Types Assigned https://www.asus.com/News/wzeltG5CjYaIwGJ0 Third Party Advisory Changed CPE Configuration OR *cpe:2.3:o:intel:active_management_technology:-:*:*:*:*:*:*:* OR *cpe:2.3:o:intel:active_management_technology_firmware:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:z170-premium_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:z170-premium:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:z170-deluxe_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:z170-deluxe:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:z170-pro_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:z170-pro:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:z170-a_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:z170-a:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:z170-ar_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:z170-ar:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:z170-e_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:z170-e:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:z170-k_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:z170-k:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:z170-p_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:z170-p:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:z170m-plus_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:z170m-plus:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:z170m-plus\/br_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:z170m-plus\/br:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:z170-p_d3_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:z170-p_d3:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:z170m-e_d3_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:z170m-e_d3:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:sabertooth_z170_mark_1_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:sabertooth_z170_mark_1:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:sabertooth_z170_s_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:sabertooth_z170_s:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_maximus_viii_extreme_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_maximus_viii_extreme:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_maximus_viii_ranger_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_maximus_viii_ranger:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_maximus_viii_formula_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_maximus_viii_formula:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_maximus_viii_hero_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_maximus_viii_hero:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_maximus_viii_hero_alpha_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_maximus_viii_hero_alpha:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_maximus_viii_gene_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_maximus_viii_gene:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_maximus_viii_impact_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_maximus_viii_impact:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:z170i_pro_gaming_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:z170i_pro_gaming:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:z170_pro_gaming_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:z170_pro_gaming:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:z170_pro_gaming\/aura_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:z170_pro_gaming\/aura:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:b150_pro_gaming_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:b150_pro_gaming:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:b150_pro_gaming\/aura_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:b150_pro_gaming\/aura:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:b150i_pro_gaming\/wifi\/aura_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:b150i_pro_gaming\/wifi\/aura:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:b150i_pro_gaming\/aura_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:b150i_pro_gaming\/aura:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:b150m_pro_gaming_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:b150m_pro_gaming:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:b150m-a_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:b150m-a:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:b150m-a_d3_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:b150m-a_d3:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:b150m-c_d3_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:b150m-c_d3:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:b150-a_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:b150-a:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:b150m-d_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:b150m-d:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:b150m-k_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:b150m-k:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:b150m-plus_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:b150m-plus:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:b150m-f_plus_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:b150m-f_plus:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:b150-plus_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:b150-plus:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:b150m-v_plus_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:b150m-v_plus:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:ex-b150m-v_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:ex-b150m-v:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:ex-b150m-v3_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:ex-b150m-v3:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:ex-b150m-v5_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:ex-b150m-v5:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:ex-b150-v7_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:ex-b150-v7:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:b150-pro_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:b150-pro:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:b150m-a\/m.2_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:b150m-a\/m.2:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:b150m-c_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:b150m-c:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:b150m-c\/br_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:b150m-c\/br:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:pio-b150m_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:pio-b150m:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:trooper_b150_d3_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:trooper_b150_d3:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:b150m-plus_d3_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:b150m-plus_d3:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:b150_pro_gaming_d3_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:b150_pro_gaming_d3:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:b150m-k_d3_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:b150m-k_d3:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:b150-pro_d3_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:b150-pro_d3:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:ex-h110m-v_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:ex-h110m-v:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:ex-h110m-v3_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:ex-h110m-v3:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110i-plus_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110i-plus:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110m-a\/dp_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110m-a\/dp:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110m-c_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110m-c:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110m-c\/br_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110m-c\/br:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110m-c\/hdmi_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110m-c\/hdmi:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110m-c\/ps_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110m-c\/ps:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110m-c2_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110m-c2:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110m-c2\/tf_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110m-c2\/tf:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110m-cs_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110m-cs:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110m-cs_x_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110m-cs_x:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110m-cs\/br_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110m-cs\/br:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110m-d\/exper\/si_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110m-d\/exper\/si:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110m-k_x_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110m-k_x:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110m-ks_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110m-ks:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110m-ks_r1_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110m-ks_r1:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110m-p\/dvi_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110m-p\/dvi:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110m-ts_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110m-ts:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110-plus_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110-plus:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110s1_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110s1:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110s2_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110s2:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110t_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110t:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110t-a_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110t-a:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110m-a\/m.2_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110m-a\/m.2:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110m-d_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110m-d:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110m-e_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110m-e:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110m-e\/m.2_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110m-e\/m.2:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110m-f_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110m-f:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110m-k_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110m-k:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110m-a_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110m-a:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:trooper_h110_d3_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:trooper_h110_d3:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110m-plus_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110m-plus:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110m-r_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110m-r:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:prime_h110m2_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:prime_h110m2:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:prime_h110m2\/fpt_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:prime_h110m2\/fpt:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:prime_h110m-p_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:prime_h110m-p:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110m-k_d3_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110m-k_d3:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h110m-a_d3_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h110m-a_d3:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h170-pro_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h170-pro:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h170i-pro_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h170i-pro:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h170_pro_gaming_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h170_pro_gaming:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h170m-plus_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h170m-plus:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h170-pro\/usb_3.1_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h170-pro\/usb_3.1:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h170m-plus\/br_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h170m-plus\/br:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h170-plus_d3_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h170-plus_d3:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:h170m-e_d3_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:h170m-e_d3:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:ex-b250-v7_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:ex-b250-v7:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:b250_mining_expert_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:b250_mining_expert:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:prime_b250m-d_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:prime_b250m-d:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:prime_b250-a_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:prime_b250-a:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:prime_b250m-a_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:prime_b250m-a:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:prime_b250m-j_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:prime_b250m-j:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:prime_b250m-plus_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:prime_b250m-plus:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:prime_b250-plus_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:prime_b250-plus:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:prime_b250m-k_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:prime_b250m-k:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:prime_b250-pro_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:prime_b250-pro:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_strix_b250i_gaming_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_strix_b250i_gaming:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_strix_b250g_gaming_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_strix_b250g_gaming:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_strix_b250h_gaming_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_strix_b250h_gaming:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_strix_b250f_gaming_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_strix_b250f_gaming:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:b250m-c_pro_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:b250m-c_pro:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:b250m-f_plus_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:b250m-f_plus:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:b250-mr_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:b250-mr:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:b250-s_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:b250-s:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:ex-b250m-v_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:ex-b250m-v:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:ex-b250m-v3_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:ex-b250m-v3:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:ex-b250m-v5_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:ex-b250m-v5:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:pio-b250i_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:pio-b250i:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:prime_b250m-c_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:prime_b250m-c:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:prime_b250m-plus\/br_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:prime_b250m-plus\/br:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:prime_h270-pro_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:prime_h270-pro:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:prime_h270-plus_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:prime_h270-plus:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_strix_h270i_gaming_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_strix_h270i_gaming:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_strix_h270f_gaming_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_strix_h270f_gaming:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:prime_h270m-plus_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:prime_h270m-plus:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_maximus_ix_extreme_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_maximus_ix_extreme:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_maximus_ix_formula_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_maximus_ix_formula:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_maximus_ix_code_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_maximus_ix_code:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_maximus_ix_apex_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_maximus_ix_apex:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_maximus_ix_hero_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_maximus_ix_hero:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:prime_z270-a_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:prime_z270-a:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:prime_z270-ar_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:prime_z270-ar:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_strix_z270e_gaming_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_strix_z270e_gaming:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_strix_z270f_gaming_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_strix_z270f_gaming:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_strix_z270g_gaming_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_strix_z270g_gaming:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_strix_z270h_gaming_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_strix_z270h_gaming:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:tuf_z270_mark_1_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:tuf_z270_mark_1:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:tuf_z270_mark_2_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:tuf_z270_mark_2:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_strix_z270h_gaming\/k1_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_strix_z270h_gaming\/k1:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:prime_z270-k_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:prime_z270-k:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:prime_z270-p_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:prime_z270-p:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_strix_z270i_gaming_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_strix_z270i_gaming:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:prime_z270m-plus_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:prime_z270m-plus:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:prime_z270m-plus\/br_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:prime_z270m-plus\/br:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:q170m-c_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:q170m-c:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:q170m-cm-b_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:q170m-cm-b:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:q170s1_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:q170s1:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:q170t_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:q170t:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:q170t_v2_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:q170t_v2:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:q170m2_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:q170m2:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:q170m2\/cdm\/si_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:q170m2\/cdm\/si:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:prime_q270m-c_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:prime_q270m-c:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:q270m-cm-a_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:q270m-cm-a:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:q270-s_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:q270-s:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:prime_j3355i-c_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:prime_j3355i-c:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_maximus_x_hero_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_maximus_x_hero:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_maximus_x_formula_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_maximus_x_formula:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_maximus_x_code_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_maximus_x_code:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_maximus_x_apex_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_maximus_x_apex:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:prime_z370-a_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:prime_z370-a:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:prime_z370-p_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:prime_z370-p:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:tuf_z370-pro_gaming_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:tuf_z370-pro_gaming:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:tuf_z370-plus_gaming_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:tuf_z370-plus_gaming:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_strix_z370-g_gaming_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_strix_z370-g_gaming:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_strix_z370-e_gaming_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_strix_z370-e_gaming:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_strix_z370-f_gaming_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_strix_z370-f_gaming:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_strix_z370-h_gaming_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_strix_z370-h_gaming:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:asus:rog_strix_z370-i_gaming_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:asus:rog_strix_z370-i_gaming:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:siemens:simatic_field_pg_m3_firmware:*:*:*:*:*:*:*:* versions up to (excluding) 6.2.61.3535 OR cpe:2.3:h:siemens:simatic_field_pg_m3:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:siemens:simatic_field_pg_m4_firmware:*:*:*:*:*:*:*:* versions up to (excluding) 18.01.06 OR cpe:2.3:h:siemens:simatic_field_pg_m4:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:siemens:simatic_field_pg_m5_firmware:*:*:*:*:*:*:*:* versions up to (excluding) 22.01.04 OR cpe:2.3:h:siemens:simatic_field_pg_m5:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:siemens:simatic_ipc677c_firmware:*:*:*:*:*:*:*:* versions up to (excluding) 6.2.61.3535 OR cpe:2.3:h:siemens:simatic_ipc677c:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:siemens:simatic_ipc427d_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:siemens:simatic_ipc427d:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:siemens:simatic_ipc427e_firmware:*:*:*:*:*:*:*:* versions up to (excluding) 21.01.07 OR cpe:2.3:h:siemens:simatic_ipc427e:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:siemens:simatic_ipc477d_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:siemens:simatic_ipc477d:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:siemens:simatic_ipc477d_pro_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:siemens:simatic_ipc477d_pro:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:siemens:simatic_ipc477e_firmware:*:*:*:*:*:*:*:* versions up to (excluding) 21.01.07 OR cpe:2.3:h:siemens:simatic_ipc477e:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:siemens:simatic_ipc547d_firmware:*:*:*:*:*:*:*:* versions up to (excluding) 7.1.91.3272 OR cpe:2.3:h:siemens:simatic_ipc547d:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:siemens:simatic_ipc547e_firmware:*:*:*:*:*:*:*:* versions up to (excluding) 9.1.41.3024 OR cpe:2.3:h:siemens:simatic_ipc547e:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:siemens:simatic_ipc627c_firmware:*:*:*:*:*:*:*:* versions up to (excluding) 6.2.61.3535 OR cpe:2.3:h:siemens:simatic_ipc627c:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:siemens:simatic_ipc627d_firmware:*:*:*:*:*:*:*:* versions up to (excluding) 9.1.41.3024 OR cpe:2.3:h:siemens:simatic_ipc627d:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:siemens:simatic_ipc647c_firmware:*:*:*:*:*:*:*:* versions up to (excluding) 6.2.61.3535 OR cpe:2.3:h:siemens:simatic_ipc647c:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:siemens:simatic_ipc647d_firmware:*:*:*:*:*:*:*:* versions up to (excluding) 9.1.41.3024 OR cpe:2.3:h:siemens:simatic_ipc647d:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:siemens:simatic_ipc677d_firmware:*:*:*:*:*:*:*:* versions up to (excluding) 9.1.41.3024 OR cpe:2.3:h:siemens:simatic_ipc677d:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:siemens:simatic_ipc827c_firmware:*:*:*:*:*:*:*:* versions up to (excluding) 6.2.61.3535 OR cpe:2.3:h:siemens:simatic_ipc827c:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:siemens:simatic_ipc827d_firmware:*:*:*:*:*:*:*:* versions up to (excluding) 9.1.41.3024 OR cpe:2.3:h:siemens:simatic_ipc827d:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:siemens:simatic_ipc847c_firmware:*:*:*:*:*:*:*:* versions up to (excluding) 6.2.61.3535 OR cpe:2.3:h:siemens:simatic_ipc847c:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:siemens:simatic_ipc847d_firmware:*:*:*:*:*:*:*:* versions up to (excluding) 9.1.41.3024 OR cpe:2.3:h:siemens:simatic_ipc847d:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:siemens:simatic_itp1000_firmware:*:*:*:*:*:*:*:* versions up to (excluding) 23.01.03 OR cpe:2.3:h:siemens:simatic_itp1000:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:siemens:simotion_p320-4s_firmware:*:*:*:*:*:*:*:* versions up to (excluding) 17.02.06.83.1 OR cpe:2.3:h:siemens:simotion_p320-4s:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:siemens:sinumerik_pcu50.5-c_firmware:*:*:*:*:*:*:*:* versions up to (excluding) 6.2.61.3535 OR cpe:2.3:h:siemens:sinumerik_pcu50.5-c:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:siemens:sinumerik_pcu50.5-p_firmware:*:*:*:*:*:*:*:* versions up to (excluding) 6.2.61.3535 OR cpe:2.3:h:siemens:sinumerik_pcu50.5-p:-:*:*:*:*:*:*:* -
CVE Modified by [email protected]
May. 11, 2018
Action Type Old Value New Value Added Reference https://cert-portal.siemens.com/productcert/pdf/ssa-892715.pdf [No Types Assigned] -
CVE Modified by [email protected]
Dec. 21, 2017
Action Type Old Value New Value Added Reference https://www.asus.com/News/wzeltG5CjYaIwGJ0 [No Types Assigned] -
Initial Analysis by [email protected]
Dec. 07, 2017
Action Type Old Value New Value Added CVSS V2 (AV:N/AC:L/Au:S/C:C/I:C/A:C) Added CVSS V3 AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H Changed Reference Type http://www.securityfocus.com/bid/101920 No Types Assigned http://www.securityfocus.com/bid/101920 Third Party Advisory, VDB Entry Changed Reference Type http://www.securitytracker.com/id/1039852 No Types Assigned http://www.securitytracker.com/id/1039852 Issue Tracking, Third Party Advisory, VDB Entry Changed Reference Type https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00086&languageid=en-fr No Types Assigned https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00086&languageid=en-fr Issue Tracking, Vendor Advisory Changed Reference Type https://security.netapp.com/advisory/ntap-20171120-0001/ No Types Assigned https://security.netapp.com/advisory/ntap-20171120-0001/ Issue Tracking, Third Party Advisory Added CWE CWE-119 Added CPE Configuration OR *cpe:2.3:o:intel:manageability_engine_firmware:*:*:*:*:*:*:*:* versions from (including) 8.0.0.0 up to (including) 8.1.71.3608 *cpe:2.3:o:intel:manageability_engine_firmware:*:*:*:*:*:*:*:* versions from (including) 9.0.0.0 up to (including) 9.1.41.3024 *cpe:2.3:o:intel:manageability_engine_firmware:*:*:*:*:*:*:*:* versions from (including) 10.0.0.0 up to (including) 10.0.55.3000 *cpe:2.3:o:intel:manageability_engine_firmware:11.0:*:*:*:*:*:*:* *cpe:2.3:o:intel:manageability_engine_firmware:11.5:*:*:*:*:*:*:* *cpe:2.3:o:intel:manageability_engine_firmware:11.6:*:*:*:*:*:*:* *cpe:2.3:o:intel:manageability_engine_firmware:11.7:*:*:*:*:*:*:* *cpe:2.3:o:intel:manageability_engine_firmware:11.10:*:*:*:*:*:*:* *cpe:2.3:o:intel:manageability_engine_firmware:11.20:*:*:*:*:*:*:* Added CPE Configuration OR *cpe:2.3:o:intel:active_management_technology:-:*:*:*:*:*:*:* -
CVE Modified by [email protected]
Nov. 24, 2017
Action Type Old Value New Value Added Reference http://www.securityfocus.com/bid/101920 [No Types Assigned] -
CVE Modified by [email protected]
Nov. 23, 2017
Action Type Old Value New Value Added Reference https://security.netapp.com/advisory/ntap-20171120-0001/ [No Types Assigned] Added Reference http://www.securitytracker.com/id/1039852 [No Types Assigned] -
CVE Modified by [email protected]
Nov. 22, 2017
Action Type Old Value New Value Removed Reference https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00086&languageid=en-fr [No Types Assigned] Added Reference https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00086&languageid=en-fr [No Types Assigned]
EPSS is a daily estimate of the probability of exploitation activity
being observed over the next 30 days. Following chart shows the EPSS
score history of the vulnerability.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2017-5712 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2017-5712
weaknesses.
CAPEC-8: Buffer Overflow in an API Call Buffer Overflow in an API Call
CAPEC-9: Buffer Overflow in Local Command-Line Utilities Buffer Overflow in Local Command-Line Utilities
CAPEC-10: Buffer Overflow via Environment Variables Buffer Overflow via Environment Variables
CAPEC-14: Client-side Injection-induced Buffer Overflow Client-side Injection-induced Buffer Overflow
CAPEC-24: Filter Failure through Buffer Overflow Filter Failure through Buffer Overflow
CAPEC-42: MIME Conversion MIME Conversion
CAPEC-44: Overflow Binary Resource File Overflow Binary Resource File
CAPEC-45: Buffer Overflow via Symbolic Links Buffer Overflow via Symbolic Links
CAPEC-46: Overflow Variables and Tags Overflow Variables and Tags
CAPEC-47: Buffer Overflow via Parameter Expansion Buffer Overflow via Parameter Expansion
CAPEC-100: Overflow Buffers Overflow Buffers
CAPEC-123: Buffer Manipulation Buffer Manipulation
Exploit Prediction
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.
1.17 }} -0.03%
score
0.85043
percentile
CVSS31 - Vulnerability Scoring System
Attack Vector
Attack Complexity
Privileges Required
User Interaction
Scope
Confidentiality
Integrity
Availability