Within hours of writing my original article about the F*CKWIT Intel CPU flaw (also known as KPTI or KAISER) things moved on quite a lot.
Google’s Project Zero vulnerability research team published technical details of serious security flaws caused by “speculative execution” that they had found not just with Intel chips, but also certain AMD and ARM processors.
Dubbed Spectre and Meltdown (and if you’re loving all these names, you should be aware that there are also cute logos), the attacks could be used to read system memory that *should* have been inaccessible.
In short, an attacker could steal sensitive information such as passwords or encryption keys from your computer’s memory. And because these flaws are in your computer’s chips, it’s not a problem that is particularly easy to properly fix without a hardware fix. Yuck.
The solution? Change the low-level software that speaks to the hardware, as the chips can no longer be trusted to do what they were supposed to be doing.
The good news is that these flaws have been known about - but kept quiet - for some months. That’s how they found the time to create the natty bug logos and consumer-friendly websites discussing the topic. The researchers who discovered the problems disclosed them to chip manufacturers and software vendors, who have been feverishly working on fixes.
So far we simply do not know if the vulnerabilities have been maliciously exploited in the wild.
Here’s what various vendors are saying to their users and customers (note - this is inevitably an incomplete list):
- Amazon AWS - Processor Speculative Execution Research Disclosure
- AMD - An Update on AMD Processor Security
- Apple - About speculative execution vulnerabilities in ARM-based and Intel CPUs
- ARM - Vulnerability of Speculative Processors to Cache Timing Side-Channel Mechanism
- Google - What Google Cloud, G Suite and Chrome customers need to know about the industry-wide CPU vulnerability. Note that if you’re a user of Chrome or Chrome OS then it makes sense to enable Site Isolation to further mitigate against the threat.
- Google Android - Android Security Bulletin—January 2018
- Intel - Intel Responds to Security Research Findings
- Microsoft - Windows Server Guidance to protect against the speculative execution side-channel vulnerabilities
- Microsoft - Windows Client Guidance for IT Pros to protect against speculative execution side-channel vulnerabilities
- Microsoft Azure - Securing Azure customers from CPU vulnerability
- Mozilla Firefox - Mitigations landing for new class of timing attack
- Redhat - Kernel Side-Channel Attacks - CVE-2017-5754 CVE-2017-5753 CVE-2017-5715
- Xen - Xen advisory
So, what should you be doing about this?
Clearly these are critical security vulnerabilities, but there is not much that consumers can do other than wait for security patches to be released and then apply them as a matter of priority.
In short: Don’t panic, make a cup of tea (coffee is also acceptable), and ensure that you install patches and security updates as they continue to roll out.
FWIW, I don’t drink tea or coffee. But I’m making an exception this morning.
For more discussion on this topic, be sure to listen to this episode of the Smashing Security podcast:Subscribe: Apple Podcasts | Spotify | Overcast | Stitcher | RSS for you nerds.