{"id":1564,"date":"2018-01-10T18:16:58","date_gmt":"2018-01-10T18:16:58","guid":{"rendered":"http:\/\/www.velocitymicro.com\/blog\/?p=1564"},"modified":"2018-06-26T15:51:39","modified_gmt":"2018-06-26T15:51:39","slug":"spectre-meltdown","status":"publish","type":"post","link":"https:\/\/www.velocitymicro.com\/blog\/spectre-meltdown\/","title":{"rendered":"Spectre and Meltdown Exploits &#8211; How are you affected?"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full\" src=\"\/images\/spectre-meltdown.jpg\" alt=\"Spectre Meltdown\" width=\"640\" height=\"300\" \/><\/p>\n<p>Much has been made in the press around the Spectre and Meltdown bugs specific to the CPU in the past week. There is quite a bit of overblown sensationalist information floating around regarding these and other exploits, so we thought it important to briefly discuss how this may affect current and future PC purchases.<\/p>\n<p>These bugs are only viable under certain circumstances within specific environments.\u00a0\u00a0To be clear, neither of these exploits are hardware flaws &#8211; they are exploits in attempts to read theoretically protected memory.\u00a0\u00a0This does not mean that anyone can read your hard drive or other areas outside of the memory space.<\/p>\n<p><strong>Additionally, this is *not* a remote exploit and has to be run locally on the machine or through a malicious application.<\/strong>\u00a0In fact, for these exploits to work, there are very specific circumstances involved, including a deep understanding of the relationships between variable data locations, and the actual content of the data.<\/p>\n<p>The exploits do not allow for a takeover or modification to the machine, or the operating system, and as such is not malware, nor does it present itself as such. From the hacking standpoint, there is next to no risk to the end-user, or smaller computer areas, due to the amount of time, effort and necessity for local access.<\/p>\n<p>For full protection, there are multiple operating system patches available that directly address this issue; however, please note that on AMD based systems, there are deeper issues and the patch could cause deep instability.\u00a0\u00a0If you are on an Intel based system, we suggest you install the following patches:<\/p>\n<ul>\n<li><a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4056897\">January 3, 2018&#8211;KB4056897 (Security-only update)<\/a><\/li>\n<li><a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4056894\">January 9, 2018&#8211;KB4056894 (Monthly Rollup)<\/a><\/li>\n<li><a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4056888\">January 3, 2018&#8211;KB4056888 (OS Build 10586.1356)<\/a><\/li>\n<li><a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4056892\">January 3, 2018&#8211;KB4056892 (OS Build 16299.192)<\/a><\/li>\n<li><a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4056891\">January 3, 2018&#8211;KB4056891 (OS Build 15063.850)<\/a><\/li>\n<li><a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4056890\">January 3, 2018&#8211;KB4056890 (OS Build 14393.2007)<\/a><\/li>\n<li><a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4056898\">January 3, 2018&#8211;KB4056898 (Security-only update)<\/a><\/li>\n<li><a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4056893\">January 3, 2018&#8211;KB4056893 (OS Build 10240.17735)<\/a><\/li>\n<li><a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4056895\">January 9, 2018&#8211;KB4056895 (Monthly Rollup)<\/a><\/li>\n<\/ul>\n<p>Please be aware, that the patches are specific to Windows 10, and Microsoft is considering instituting a patch for Windows 7, but since it is end of life, they have not yet made the decision to do so.<\/p>\n<p>There will likely be firmware updates to the BIOS soon to further mitigate the theoretical threat, but until that point, the Microsoft series of patches have shown to be very effective. If\/when a firmware or BIOS update is available, we will update this article with that information. We are working with our board manufacturer partners to ensure proper testing is conducted before rolling out those updates.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Much has been made in the press around the Spectre and Meltdown bugs specific to the CPU in the past&hellip;<\/p>\n","protected":false},"author":6,"featured_media":-1,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"fifu_image_url":"http:\/\/www.velocitymicro.com\/images\/spectre-meltdown.jpg","fifu_image_alt":"","footnotes":""},"categories":[21],"tags":[],"class_list":["post-1564","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-pc-news"],"_links":{"self":[{"href":"https:\/\/www.velocitymicro.com\/blog\/wp-json\/wp\/v2\/posts\/1564","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.velocitymicro.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.velocitymicro.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.velocitymicro.com\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/www.velocitymicro.com\/blog\/wp-json\/wp\/v2\/comments?post=1564"}],"version-history":[{"count":3,"href":"https:\/\/www.velocitymicro.com\/blog\/wp-json\/wp\/v2\/posts\/1564\/revisions"}],"predecessor-version":[{"id":1674,"href":"https:\/\/www.velocitymicro.com\/blog\/wp-json\/wp\/v2\/posts\/1564\/revisions\/1674"}],"wp:attachment":[{"href":"https:\/\/www.velocitymicro.com\/blog\/wp-json\/wp\/v2\/media?parent=1564"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.velocitymicro.com\/blog\/wp-json\/wp\/v2\/categories?post=1564"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.velocitymicro.com\/blog\/wp-json\/wp\/v2\/tags?post=1564"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}