Tracker / CVE-2018-3639
CVE-2018-3639
Medium 5.5
Systems with microprocessors utilizing speculative execution and speculative execution of memory reads before the addresses of all prior memory writes are known may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis, aka Speculative Store Bypass (SSB), Variant 4.
Affected products and versions
| arm | cortex-a |
|---|---|
| canonical | ubuntu_linux |
| debian | debian_linux |
| intel | atom_c |
| intel | atom_e |
| 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 | pentium |
| intel | pentium_j |
| intel | pentium_silver |
| intel | xeon_e-1105c |
| intel | xeon_e3 |
| intel | xeon_e3_1105c_v2 |
| intel | xeon_e3_1125c_v2 |
| 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 |
| intel | xeon_e3_1230 |
| intel | xeon_e3_1230_v2 |
| intel | xeon_e3_1230_v3 |
| intel | xeon_e3_1230_v5 |
| intel | xeon_e3_1230_v6 |
| intel | xeon_e3_1230l_v3 |
| intel | xeon_e3_1231_v3 |
| intel | xeon_e3_1235 |
| intel | xeon_e3_1235l_v5 |
| intel | xeon_e3_1240 |
| intel | xeon_e3_1240_v2 |
| intel | xeon_e3_1240_v3 |
| intel | xeon_e3_1240_v5 |
| intel | xeon_e3_1240_v6 |
| intel | xeon_e3_1240l_v3 |
| intel | xeon_e3_1240l_v5 |
| intel | xeon_e3_1241_v3 |
| intel | xeon_e3_1245 |
| intel | xeon_e3_1245_v2 |
| intel | xeon_e3_1245_v3 |
| intel | xeon_e3_1245_v5 |
| intel | xeon_e3_1245_v6 |
| intel | xeon_e3_1246_v3 |
| intel | xeon_e3_1258l_v4 |
| intel | xeon_e3_1260l |
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.