Serious New Security Issues (Meltdown/Spectre) and How to Address Them

chip blog

A Serious Problem

Over the past few days you may have heard some news about the new security flaws-“Spectre” and “Meltdown”-  affecting the processors on computers, mobile phones & tablets and in the cloud. Current CPU chips from Intel, AMD, Qualcomm, ARM & others have this flaw, which means that these risks cover virtually every computing device. Windows, Linux & Apple products are all affected, as well as embedded processors relying on these CPU chips. This vulnerability is so significant that the US Dept. of Homeland Security has issued an alert.

This issue is caused by a flaw in the fundamental design of these chips called “speculative processing”, which is used to accelerate them. Estimating next steps in an operation & speculatively processing them does indeed speed up these chips (& the computers that run them). However, it also allows a hacker to jump ahead and grab sensitive information (like passwords) prior to the all-important step of being authenticated.

Risks to the Cloud

These vulnerabilities affect cloud services, including those from Amazon Web Services (AWS), Google, Oracle, ADP, etc. and most external hosting environments. Cloud services are particularly at risk, because they rely on virtualization – the creation of virtual CPUs within a physical CPU.   The “wall jumping” nature of the Spectre and Meltdown vulnerabilities allows them to potentially cross the electronic barriers between virtual CPUs (& between different companies hosted on those cloud services).

Spectre vs Meltdown

Spectre breaks the designed isolation between different applications. It allows an attacker to trick error-free programs such as browsers (Firefox, Explorer, Chrome, Safari, Edge, etc.) and gain access to password information. The built-in safety checks in many applications ironically may make them more susceptible to Spectre. All of the common CPU chips today have inherent Spectre vulnerabilities.

Meltdown breaks the fundamental isolation between user applications and the operating system. Any application in theory could steal your data, including simple things such as javascript from a web page viewed in a browser. Every Intel processor with speculative processing is potentially affected. This is effectively every computer with “Intel Inside” since 1995.

Immediate Steps to Take

The best steps to take right now are to patch operating systems and browsers, as well as updating the BIOS and firmware on all affected computers (other than those based on AMD chips, which should hold for the moment). Major computer manufacturers and browser developers are rush-releasing patches to protect their systems.

1. First, check your hardware configurations to see what CPU chip your computers are based on. (Here is how to do that on a Windows 10 machineon a Mac , and on Linux-based  computers.

2. Install patches for vulnerable OS’s, BIOS (Basic Input Output System – software stored on a small motherboard memory chip that initializes hardware and manages the flow of data between the CPU & peripherals) and firmware (embedded software for hardware component control) on phones, tablets & computers using Intel & ARD chips. (Wait on those using AMD chips for now, see below):

  • Android-  Google has issued instructions on how to test your phone’s security level and released patches to its manufacturing partners & supported phones.  It encourages all users to accept the latest security updates.
  • Apple (iPhone, iPad, MAC)-  Yesterday Apple released patches to its mobile platforms (phones/ iPads) and computer systems. iPhones and Tablets should be updated to iOS 11.2.2. Mac OS’s should be updated to 10.13.2 (High Sierra) with the supplemental security update installed. There is some risk that older applications which run on Sierra (10.12) may not run on the new OS.  We have seen this issue with Quickbooks 2014, for example. In this case, another option is to install the new Safari 11.0.2 update for Yosemite (10.11) and Sierra (10.12).
  • Intel-based Microsoft PC’s- Intel has released a tool to test the vulnerability of individual PC’s and a security advisory describing the affected models. This tool should be run to detect possible vulnerabilities and then the OS (for other than AMD-based computers at this point) should be updated (cautiously), following these instructions (Windows). In addition the computer manufacturers’ support (scroll down for a helpful list) should be contacted for instructions on updating the firmware and BIOS.
  • Intel-based Linux PC’s- Intel has released a tool to test the vulnerability of individual PC’s and a security advisory describing the affected models. This tool should be run to detect possible vulnerabilities and then the OS (for other than AMD-based computers at this point) should be updated (cautiously), following these instructions (Linux- should be updated to version 4.14.12). In addition the computer manufacturers’ support (scroll down for a helpful list) should be contacted for instructions on updating the firmware and BIOS.
  • Surface Tablets- These are not vulnerable (whew!) due to their design.

3. Update Browsers:

  • Chrome-  Update to the latest version (63.0.3239.132) by clicking on the About Chrome tab & running the auto-update. Google has promised full protection in Chrome in their planned 64.0 release on Jan. 23, 2018.
  • Explorer/Edge- Microsoft is bundling patches (which actually slow the browser execution a bit) to address these vulnerabilities in with its Windows Updates
  • Firefox- should be updated to version 57.0.4. This contains a protective security patch.
  • Safari- these are addressed by Apple in conjunction with its iOS and OS updates. For older OS’s (Yosemite and Sierra) these are available as a direct update via the App Store – see Safari 11.0.2 update.

4. Update any Virtualization software. These pieces of software allow multiple “virtual” CPU’s to run on a single hardware server. The name of the Spectre and Meltdown vulnerabilities could allow malicious applications to jump across these virtual CPUs. The most commonly-used virtualization system is VMWare from Dell/EMC; their security updates are available here.

5. Get Information from your Cloud Partners on their mitigation efforts. These vulnerabilities affect all of them, and therefore you. Consequently your cloud vendors, hosting partners & embedded systems manufacturers need to provide a plan and timeline for addressing these vulnerabilities.

6. Repeat at Home. To state the obvious, these risks occur at home as well.   Follow the same protocol for all home systems and phones.

7. Be wary of possible phishing attempts mimicking Microsoft fixes! Microsoft patching happens automatically via the internal Windows Update and does NOT require clicking on a link or pop-up to activate! Only install software or patches from the manufacturer (& confirm that the links go to urls from, etc. and not or, etc.)

Patch Performance Issues

Since most of these patches are new and not fully tested due to time pressures there is a need to proceed carefully. Microsoft patches are known to interfere with some antivirus solutions as well. Anti-virus/malware protection software may need to be turned off during installs and updated or replaced on an on-going basis. In addition, Microsoft updates are making some computers based on AMD chips unbootable (inoperable, because they will not start up). Each company blames the other but a fix is likely to emerge within a week or so.

In addition, since the patches are slowing fundamental processes important to computer speeds, there may be visible performance degradation (cloud services, phones, and laptops will run slower). It appears that patches for Meltdown affect machine performance more significantly than Spectre.

The Longer Term Fix

A real fix vs. patches requires new chip designs and new hardware.   These systems will be accelerated into production and should be on the market within 6 months to a year.

Body1 Approach

We develop and host software and websites on all major OS platforms (Windows, Linux, Mac-OS, Android & iOS). We are closely monitoring this situation and following all of our own advice in this advisory. We have made significant progress in protecting all of our (and your!) systems. In addition, as we continue to upgrade our data centers, we will deploy new redundant hardware with new chip sets that do not have these vulnerabilities.

For More Information

We at Body1 are dedicated to a secure web and are here to help. Please do not hesitate to contact any of us if you have any questions.


Can the Compassion of “The Crowd” Reduce Suicide?

HodlerDespondency1887WinterthurA web

Hodler, Despondency, 1887, Winterthur

Something we think a lot about here at Body1 is how to “Connect People with the Health Information that Matters Most to Them”.   In fact, we’ve made that our Mission.   We seek to apply it in our work, and in the ideas which we share.

Here’s one idea.  There’s a huge social opportunity to leverage digital for suicide prevention. Especially so, since suicide is a huge mental health issue that is largely unresolved.   It is a top 10 cause of death in America, 3rd behind only cancer and heart disease in years of life lost.   In the most recent full reporting year (2012), the US Centers for Disease Control and Prevention (CDC) report 40,600 suicides, equivalent to someone dying every 13 minutes.

Given the immediacy of the need and the ubiquitous of smartphones, digital could offer a solution.  A 24 hour/day, 7 day/week, 365 day/year (24×7, 365) app that video links to a trained peer counselor is one possible approach.

There are some big questions to be answered first, including (but not limited to):

1. How to staff with appropriately trained personnel?
(one approach- could be drawn from a pool of *trained* volunteers with a round robin telephone routing),

2. How to market & distribute
(possibly via health plans, Apple, Google, telco’s, etc);

3. Who funds?
(options include CDC, state Health depts, crowdfunded?)

This seems to us like a wonderful way for digital to contribute to the social good.  Thoughts? Comments?