Tracker / CVE-2017-5753
CVE-2017-5753
Medium 5.6
Systems with microprocessors utilizing speculative execution and branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis.
Affected products and versions
| arm | cortex-a12_firmware |
|---|---|
| arm | cortex-a15_firmware |
| arm | cortex-a17_firmware |
| arm | cortex-a57_firmware |
| arm | cortex-a72_firmware |
| arm | cortex-a73_firmware |
| arm | cortex-a75_firmware |
| arm | cortex-a76_firmware |
| arm | cortex-a77_firmware |
| arm | cortex-a78_firmware |
| arm | cortex-a78ae_firmware |
| arm | cortex-a8_firmware |
| arm | cortex-a9_firmware |
| arm | cortex-r7_firmware |
| arm | cortex-r8_firmware |
| arm | cortex-x1_firmware |
| arm | neoverse_n1_firmware |
| arm | neoverse_n2_firmware |
| canonical | ubuntu_linux |
| debian | debian_linux |
| intel | atom_c |
| intel | atom_e |
| intel | atom_x3 |
| intel | atom_x5-e3930 |
| intel | atom_x5-e3940 |
| intel | atom_x7-e3950 |
| intel | atom_z |
| intel | celeron_j |
| intel | celeron_n |
| intel | core_i3 |
| intel | core_i5 |
| intel | core_i7 |
| intel | core_m |
| intel | core_m3 |
| intel | core_m5 |
| intel | core_m7 |
| intel | pentium_j |
| intel | pentium_n |
| intel | xeon |
| intel | xeon_bronze_3104 |
| intel | xeon_bronze_3106 |
| intel | xeon_e-1105c |
| intel | xeon_e3 |
| intel | xeon_e3_1105c_v2 |
| intel | xeon_e3_1125c |
| intel | xeon_e3_1125c_v2 |
| intel | xeon_e3_1220 |
| intel | xeon_e3_12201 |
| intel | xeon_e3_12201_v2 |
| intel | xeon_e3_1220_v2 |
| intel | xeon_e3_1220_v3 |
| intel | xeon_e3_1220_v5 |
| intel | xeon_e3_1220_v6 |
| intel | xeon_e3_1220l_v3 |
| intel | xeon_e3_1225 |
| intel | xeon_e3_1225_v2 |
| intel | xeon_e3_1225_v3 |
| intel | xeon_e3_1225_v5 |
| intel | xeon_e3_1225_v6 |
| intel | xeon_e3_1226_v3 |
Analysis
This page is not indexable yet.Until it carries original analysis — what it actually exposes, how to check in two minutes whether a system was touched, what to do if it was — the page stays noindex. The database decides that, not the template.